-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Fix for GET /_migration/deprecations doesn't report node deprecations if low watermark exceeded and GET /_migration/deprecations doesn't report node-level failures properly #137964
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
… if low watermark exceeded and GET /_migration/deprecations doesn't report node-level failures properly Closes elastic#137010 Closes elastic#137004
Collaborator
|
Hi @alexey-ivanov-es, I've created a changelog YAML for you. |
Collaborator
|
Pinging @elastic/es-core-infra (Team:Core/Infra) |
jdconrad
approved these changes
Nov 13, 2025
This was referenced Nov 13, 2025
Collaborator
alexey-ivanov-es
added a commit
to alexey-ivanov-es/elasticsearch
that referenced
this pull request
Nov 13, 2025
… if low watermark exceeded and GET /_migration/deprecations doesn't report node-level failures properly (elastic#137964) Fix for GET /_migration/deprecations doesn't report node deprecations if low watermark exceeded and GET /_migration/deprecations doesn't report node-level failures properly Closes elastic#137010 Closes elastic#137004
alexey-ivanov-es
added a commit
to alexey-ivanov-es/elasticsearch
that referenced
this pull request
Nov 13, 2025
… if low watermark exceeded and GET /_migration/deprecations doesn't report node-level failures properly (elastic#137964) Fix for GET /_migration/deprecations doesn't report node deprecations if low watermark exceeded and GET /_migration/deprecations doesn't report node-level failures properly Closes elastic#137010 Closes elastic#137004
elasticsearchmachine
pushed a commit
that referenced
this pull request
Nov 13, 2025
… if low watermark exceeded and GET /_migration/deprecations doesn't report node-level failures properly (#137964) (#138034) Fix for GET /_migration/deprecations doesn't report node deprecations if low watermark exceeded and GET /_migration/deprecations doesn't report node-level failures properly Closes #137010 Closes #137004
Contributor
Author
|
Was backported as part of #138115 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
auto-backport
Automatically create backport pull requests when merged
>bug
:Core/Infra/Core
Core issues without another label
Team:Core/Infra
Meta label for core/infra team
v8.19.8
v9.1.8
v9.2.2
v9.3.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.
Closes #137010
Closes #137004