-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Remove usage of .watches system index in full cluster restart. #65884
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
Remove usage of .watches system index in full cluster restart. #65884
Conversation
Make use for the cluster state api to check the index.format setting of the .watches index instead of querying the index settings api. This removes the last direct usage of .watches index mentioned in elastic#62501.
|
Pinging @elastic/es-core-features (Team:Core/Features) |
|
@elasticmachine run elasticsearch-ci/2 |
| } | ||
| } | ||
| // Verify .watches index format: | ||
| var getClusterStateResponse = entityAsMap(client().performRequest(new Request("GET", "/_cluster/state"))); |
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.
nit: GET /_cluster/state/metadata/.watches would be tiny bit more efficient.
jakelandis
left a comment
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
Backport elastic#65884 to 7.x branch. Make use for the cluster state api to check the index.format setting of the .watches index instead of querying the index settings api. This removes the last direct usage of .watches index mentioned in elastic#62501.
Make use for the cluster state api to check the index.format setting
of the .watches index instead of querying the index settings api.
This removes the last direct usage of .watches index mentioned in #62501.