Skip to content

[7.17] Correct context for batched reroute notifications (#83019) #83166

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

Merged

Conversation

DaveCTurner
Copy link
Contributor

Backports the following commits to 7.17:

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 DaveCTurner added auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport labels Jan 26, 2022
@elasticsearchmachine elasticsearchmachine merged commit 920309b into elastic:7.17 Jan 26, 2022
@DaveCTurner DaveCTurner deleted the backport/7.17/pr-83019 branch January 26, 2022 17:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport v7.17.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants