Handle wrapped IO exceptions in test cluster distribution syncing #82288
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Pinging @elastic/es-delivery (Team:Delivery) |
mark-vieira
added
auto-backport-and-merge
|
@elasticmachine update branch |
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.
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
…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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Third attempt at sorting out this problem after #82154 didn't do the trick. The issue is that
FileTreeIteratorwraps the root cause exception in anUncheckedIOExceptionso to detect this scenario properly we actually have to inspect the cause.