-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Protect against stuck migration due to disabled allocation #52569
Comments
Pinging @elastic/es-ui (Team:Elasticsearch UI) |
I think we are hitting this in ECK, see elastic/cloud-on-k8s#2352. Users are free to perform any change on the Elasticsearch specification that may lead to a rolling upgrade (eg. version change, but also memory requirements changes, configuration changes, etc.). During rolling upgrades we disable shards allocation. Concurrently, users may require a version upgrade of Kibana. |
Pinging @elastic/kibana-platform (Team:Platform) |
This will probably be addressed by #75780 |
Kibana version: 7.4
Elasticsearch version: 7.4
If Elasticsearch allocation is disabled when Kibana is upgraded, the upgrade will get stuck, requiring intervention, even after allocation has been re-enabled.
The text was updated successfully, but these errors were encountered: