Dispatch ClusterStateAction#buildResponse to executor #103435
Merged
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
If waiting for a particular cluster state (e.g. on the CCR leader) we will compute the resulting cluster state and serialize it on the cluster applier thread, which can be too expensive in a large cluster for this thread. With this commit we dispatch the final action back to the original executor.
DaveCTurner
added
>bug
:Distributed/Distributed
|
Pinging @elastic/es-distributed (Team:Distributed) |
|
Hi @DaveCTurner, I've created a changelog YAML for you. |
idegtiarenko
approved these changes
Dec 14, 2023
DaveCTurner
added
auto-merge
DaveCTurner
deleted the
2023/12/14/TransportClusterStateAction-fork-buildResponse
branch
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this pull request
Dec 14, 2023
If waiting for a particular cluster state (e.g. on the CCR leader) we will compute the resulting cluster state and serialize it on the cluster applier thread, which can be too expensive in a large cluster for this thread. With this commit we dispatch the final action back to the original executor.
This was referenced Dec 14, 2023
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this pull request
Dec 14, 2023
If waiting for a particular cluster state (e.g. on the CCR leader) we will compute the resulting cluster state and serialize it on the cluster applier thread, which can be too expensive in a large cluster for this thread. With this commit we dispatch the final action back to the original executor.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Dec 14, 2023
) If waiting for a particular cluster state (e.g. on the CCR leader) we will compute the resulting cluster state and serialize it on the cluster applier thread, which can be too expensive in a large cluster for this thread. With this commit we dispatch the final action back to the original executor.
DaveCTurner
added a commit
that referenced
this pull request
Dec 14, 2023
#103443) If waiting for a particular cluster state (e.g. on the CCR leader) we will compute the resulting cluster state and serialize it on the cluster applier thread, which can be too expensive in a large cluster for this thread. With this commit we dispatch the final action back to the original executor.
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.
If waiting for a particular cluster state (e.g. on the CCR leader) we
will compute the resulting cluster state and serialize it on the cluster
applier thread, which can be too expensive in a large cluster for this
thread. With this commit we dispatch the final action back to the
original executor.