Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ignore errors syncing ephemeral files in test clusters #82154

Merged
merged 1 commit into from
Jan 4, 2022

Conversation

mark-vieira
Copy link
Contributor

#81482 didn't completely fix this underlying issue as FileTreeWalker will throw an exception it seems if a file disappears during traversal. Let's make this more robust and catch this exception and simply ignore if it's complaining about a missing .attach_pid file.

@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-delivery (Team:Delivery)

@elasticsearchmachine
Copy link
Collaborator

💚 Backport successful

Status Branch Result
8.0
7.17
7.16

elasticsearchmachine pushed a commit that referenced this pull request Jan 6, 2022
…2288)

Third attempt at sorting out this problem after #82154 didn't do the
trick. The issue is that `FileTreeIterator` wraps the root cause
exception in an `UncheckedIOException` so to detect this scenario
properly we actually have to inspect the cause.
mark-vieira added a commit to mark-vieira/elasticsearch that referenced this pull request Jan 6, 2022
…astic#82288)

Third attempt at sorting out this problem after elastic#82154 didn't do the
trick. The issue is that `FileTreeIterator` wraps the root cause
exception in an `UncheckedIOException` so to detect this scenario
properly we actually have to inspect the cause.
mark-vieira added a commit to mark-vieira/elasticsearch that referenced this pull request Jan 6, 2022
…astic#82288)

Third attempt at sorting out this problem after elastic#82154 didn't do the
trick. The issue is that `FileTreeIterator` wraps the root cause
exception in an `UncheckedIOException` so to detect this scenario
properly we actually have to inspect the cause.
mark-vieira added a commit to mark-vieira/elasticsearch that referenced this pull request Jan 6, 2022
…astic#82288)

Third attempt at sorting out this problem after elastic#82154 didn't do the
trick. The issue is that `FileTreeIterator` wraps the root cause
exception in an `UncheckedIOException` so to detect this scenario
properly we actually have to inspect the cause.
elasticsearchmachine pushed a commit that referenced this pull request Jan 6, 2022
…2288) (#82300)

Third attempt at sorting out this problem after #82154 didn't do the
trick. The issue is that `FileTreeIterator` wraps the root cause
exception in an `UncheckedIOException` so to detect this scenario
properly we actually have to inspect the cause.
elasticsearchmachine pushed a commit that referenced this pull request Jan 6, 2022
…2288) (#82298)

Third attempt at sorting out this problem after #82154 didn't do the
trick. The issue is that `FileTreeIterator` wraps the root cause
exception in an `UncheckedIOException` so to detect this scenario
properly we actually have to inspect the cause.
elasticsearchmachine pushed a commit that referenced this pull request Jan 6, 2022
…2288) (#82299)

Third attempt at sorting out this problem after #82154 didn't do the
trick. The issue is that `FileTreeIterator` wraps the root cause
exception in an `UncheckedIOException` so to detect this scenario
properly we actually have to inspect the cause.
astefan pushed a commit to astefan/elasticsearch that referenced this pull request Jan 7, 2022
astefan pushed a commit to astefan/elasticsearch that referenced this pull request Jan 7, 2022
…astic#82288)

Third attempt at sorting out this problem after elastic#82154 didn't do the
trick. The issue is that `FileTreeIterator` wraps the root cause
exception in an `UncheckedIOException` so to detect this scenario
properly we actually have to inspect the cause.
astefan pushed a commit to astefan/elasticsearch that referenced this pull request Jan 7, 2022
astefan pushed a commit to astefan/elasticsearch that referenced this pull request Jan 7, 2022
…astic#82288)

Third attempt at sorting out this problem after elastic#82154 didn't do the
trick. The issue is that `FileTreeIterator` wraps the root cause
exception in an `UncheckedIOException` so to detect this scenario
properly we actually have to inspect the cause.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Delivery/Build Build or test infrastructure >non-issue Team:Delivery Meta label for Delivery team v7.16.3 v7.17.0 v8.0.0 v8.1.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants