-
Notifications
You must be signed in to change notification settings - Fork 25.4k
Run TransportGetStatusAction
on local node
#129367
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
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. Relates elastic#101805
Pinging @elastic/es-data-management (Team:Data Management) |
Hi @nielsbauman, I've created a changelog YAML for you. |
45 tasks
dakrone
approved these changes
Jun 12, 2025
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.
LGTM, thanks!
nielsbauman
added a commit
to nielsbauman/elasticsearch
that referenced
this pull request
Jun 13, 2025
Since elastic#129367 we run the `_ilm/status` API on the local node, which could cause issues in tests that assume the API runs on the master node - i.e. they assumed that once the assertion passed, all nodes in the cluster would have that cluster state, which is not true.
nielsbauman
added a commit
to nielsbauman/elasticsearch
that referenced
this pull request
Jun 13, 2025
Since elastic#129367 we run the `_ilm/status` API on the local node, which could cause issues in tests that assume the API runs on the master node (i.e. they assumed that once the assertion passed, all nodes in the cluster would have that cluster state, which is not true).
nielsbauman
added a commit
that referenced
this pull request
Jun 13, 2025
Since #129367 we run the `_ilm/status` API on the local node, which could cause issues in tests that assume the API runs on the master node (i.e. they assumed that once the assertion passed, all nodes in the cluster would have that cluster state, which is not true).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Data Management/ILM+SLM
Index and Snapshot lifecycle management
>enhancement
Team:Data Management
Meta label for data/management team
v9.1.0
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.
Relates #101805