You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As pointed out in https://discuss.elastic.co/t/gke-upgrade-and-pdb/215661, GKE auto-upgrades respect PDB only for limited amount of time (1 hour). This might interfere with relocating shards which would be triggered when:
it takes more than 1 minute for a given ES node to come back, or
cluster is using local storage that is removed on k8s node upgrade.
We should investigate the consequences of this behaviour for ECK and ECK managed ES clusters on GKE and other managed k8s solutions.
Maybe we should also give configuration recommendations around this.
The text was updated successfully, but these errors were encountered:
As pointed out in https://discuss.elastic.co/t/gke-upgrade-and-pdb/215661, GKE auto-upgrades respect PDB only for limited amount of time (1 hour). This might interfere with relocating shards which would be triggered when:
We should investigate the consequences of this behaviour for ECK and ECK managed ES clusters on GKE and other managed k8s solutions.
Maybe we should also give configuration recommendations around this.
The text was updated successfully, but these errors were encountered: