Do not return Cluster State in /_cluster/reroute API response #96511
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
volodk85 added >breaking :Distributed Coordination/Allocation 
Collaborator
| Hi @volodk85, I've created a changelog YAML for you. Note that since this PR is labelled |
volodk85 changed the title Collaborator
| Hi @volodk85, I've updated the changelog YAML for you. Note that since this PR is labelled |
Contributor
| Superseded by #114231. |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
9 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.
Removes cluster state from /_cluster/reroute API response.
This PR brings a breaking change on REST API level. Affected API is https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-reroute.html
Various cluster state
metricwere rendered insidestatefield in the API response. Ifstatefield is gone, there is no place where to show concerning metrics. Note that in #88978 team agreed to removemetricsin the next major version (which is going to be 9.0.x) Thus, it makes sense to removemetricsentirely within this PR.I'd structure changes to this api in two phases: 1) Change API signature (this PR) and 2) Clean-up of AllocationService (as per commend in code)
This is DRAFT PR. DO NOT MERGE until work on ES 9.0 version is kicked off
REST compatibility is expected to fail at this time.
Closes #88978