Run TransportEnrichStatsAction on local node
#121256
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
This action solely needs the cluster state, it can run on any node. Additionally, it needs to be cancellable to avoid doing unnecessary work after a client failure or timeout.
nielsbauman
added
>enhancement
:Data Management/Ingest Node
Collaborator
|
Pinging @elastic/es-data-management (Team:Data Management) |
Collaborator
|
Hi @nielsbauman, I've created a changelog YAML for you. |
45 tasks
Member
|
Is this missing a call to |
Contributor
Author
fzowl
pushed a commit
to voyage-ai/elasticsearch
that referenced
this pull request
Feb 4, 2025
This action solely needs the cluster state, it can run on any node. Additionally, it needs to be cancellable to avoid doing unnecessary work after a client failure or timeout.
nielsbauman
added a commit
to nielsbauman/elasticsearch
that referenced
this pull request
Feb 5, 2025
In elastic#121256, we changed the superclass of the request to `LocalClusterStateRequest` to make the action run on the local node instead of the master node. Most of the actions that have been updated thusfar to run on the local node used to extend `MasterNodeReadRequest` and thus serialized a `local` field. This request class, however, extended `MasterNodeRequest`, meaning that it didn't serialize that field.
nielsbauman
added a commit
that referenced
this pull request
Feb 6, 2025
In #121256, we changed the superclass of the request to `LocalClusterStateRequest` to make the action run on the local node instead of the master node. Most of the actions that have been updated thusfar to run on the local node used to extend `MasterNodeReadRequest` and thus serialized a `local` field. This request class, however, extended `MasterNodeRequest`, meaning that it didn't serialize that field.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This action solely needs the cluster state, it can run on any node. Additionally, it needs to be cancellable to avoid doing unnecessary work after a client failure or timeout.
Relates #101805