Correct context for batched reroute notifications #83019
Merged
Conversation
This file contains hidden or 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
Today the `BatchedRerouteService` completes its listeners in the thread context of the `reroute()` call that actually triggered the reroute, which will be the correct context only if no batching took place. With this commit we make sure to complete each listener in the context in which it was passed to the corresponding `reroute()` call.
DaveCTurner
added
>bug
:Distributed Coordination/Allocation
elasticmachine
added
the
Team:Distributed (Obsolete)
|
Pinging @elastic/es-distributed (Team:Distributed) |
idegtiarenko
approved these changes
Jan 25, 2022
|
Hi @DaveCTurner, I've created a changelog YAML for you. |
DaveCTurner
added
auto-backport-and-merge
auto-merge-without-approval
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this pull request
Jan 26, 2022
Today the `BatchedRerouteService` completes its listeners in the thread context of the `reroute()` call that actually triggered the reroute, which will be the correct context only if no batching took place. With this commit we make sure to complete each listener in the context in which it was passed to the corresponding `reroute()` call.
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this pull request
Jan 26, 2022
Today the `BatchedRerouteService` completes its listeners in the thread context of the `reroute()` call that actually triggered the reroute, which will be the correct context only if no batching took place. With this commit we make sure to complete each listener in the context in which it was passed to the corresponding `reroute()` call.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Jan 26, 2022
Today the `BatchedRerouteService` completes its listeners in the thread context of the `reroute()` call that actually triggered the reroute, which will be the correct context only if no batching took place. With this commit we make sure to complete each listener in the context in which it was passed to the corresponding `reroute()` call.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Jan 26, 2022
Today the `BatchedRerouteService` completes its listeners in the thread context of the `reroute()` call that actually triggered the reroute, which will be the correct context only if no batching took place. With this commit we make sure to complete each listener in the context in which it was passed to the corresponding `reroute()` call.
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.
Today the
BatchedRerouteServicecompletes its listeners in the threadcontext of the
reroute()call that actually triggered the reroute,which will be the correct context only if no batching took place. With
this commit we make sure to complete each listener in the context in
which it was passed to the corresponding
reroute()call.