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

Handle partial failure retrieving segments in SegmentCountStep #46556

Conversation

dakrone
Copy link
Member

@dakrone dakrone commented Sep 10, 2019

Since the IndicesSegmentsRequest scatters to all shards for the index,
it's possible that some of the shards may fail. This adds failure
handling and logging (since this is a best-effort step in the first
place) for this case.

Since the `IndicesSegmentsRequest` scatters to all shards for the index,
it's possible that some of the shards may fail. This adds failure
handling and logging (since this is a best-effort step in the first
place) for this case.
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features

Copy link
Contributor

@gwbrown gwbrown left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM with one super minor thing I'm not even sure is worth addressing.

More mockito than I expected to see in a PR from you :) But I understand why.

@dakrone
Copy link
Member Author

dakrone commented Sep 10, 2019

More mockito than I expected to see in a PR from you :) But I understand why.

Hah, this is mostly me copying the other tests in the class rather than writing one from scratch ;)

@dakrone dakrone merged commit f907b60 into elastic:master Sep 11, 2019
@dakrone dakrone deleted the ilm-handle-shard-failures-checking-segment-count branch September 11, 2019 16:28
dakrone added a commit that referenced this pull request Sep 11, 2019
Since the `IndicesSegmentsRequest` scatters to all shards for the index,
it's possible that some of the shards may fail. This adds failure
handling and logging (since this is a best-effort step in the first
place) for this case.
dakrone added a commit that referenced this pull request Sep 11, 2019
Since the `IndicesSegmentsRequest` scatters to all shards for the index,
it's possible that some of the shards may fail. This adds failure
handling and logging (since this is a best-effort step in the first
place) for this case.
@dakrone dakrone removed the v6.8.4 label Sep 11, 2019
@colings86 colings86 added v7.4.0 and removed v7.4.1 labels Sep 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants