-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
migrations: handle 200 response code from _cluster/health API on timeout #117879
Conversation
Pinging @elastic/kibana-core (Team:Core) |
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
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
Please remember to set the flag for the backport.
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.
approve
💔 Backport failed
Successful backport PRs will be merged automatically after passing CI. To backport manually run: |
Summary
Fixes Kibana to handle the breaking ES change introduced in elastic/elasticsearch#78968
In 7.16 this will produce a deprecation warning every time Kibana starts up, so we need to backport this fix. In the 7.x backport we also need to set the
return_200_for_cluster_health_timeout=true
query paramater to thecluster/_health
API to prevent deprecation warnings.Fixes #117856
Checklist
Delete any items that are not applicable to this PR.
Risk Matrix
Delete this section if it is not applicable to this PR.
Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.
When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:
For maintainers