-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Use general cluster state batching mechanism for shard started #15023
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
Conversation
|
@bleskes I'll rebase this pull request on master when #14899 is reintegrated there. The salient commit for this review is thus 8f7194d52650180c08d3a9e32acc26e47f6061f7 pending #14899 (all the changes for that commit are in ShardStateAction.java and some minor modifications in AllocationService.java). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need this processed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed in b58d82f.
|
LGTM. Left a more general comment about how we report failures with the new batching. |
This commit modifies the handling of shard started cluster state updates to use the general cluster state batching mechanism. An advantage of this approach is we now get correct per-listener notification on failures.
Use general cluster state batching mechanism for shard started
This commit modifies the handling of shard started cluster state updates
to use the general cluster state batching mechanism. An advantage of
this approach is we now get correct per-listener notification on
failures.
Relates #14899, relates #14725