[elasticsearch] Add a way for the readiness check to accept yellow state temporarily
See original GitHub issueDescribe the feature: Enable manually allowing the readiness check to accept yellow state temporarily. E.g. by creating a file inside the pod, which would be deleted automatically once it reaches the green state.
Describe a specific use case for the feature: When all the nodes crash and then are starting again, e.g. after depleting memory/heap on all nodes, all the nodes wait for the green state, even though the cluster is operational once it reaches the yellow state.
Updating the statefulset with clusterHealthCheckParams
set without wait_for_green
isn’t the best solution as it entails another restart of the whole cluster.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:12 (4 by maintainers)
Top Results From Across the Web
Red or yellow cluster status | Elasticsearch Guide [8.5] | Elastic
A red or yellow cluster status indicates one or more shards are missing or unallocated. These unassigned shards increase your risk of data...
Read more >Elasticsearch Yellow Status - Opster
Overview. Yellow status indicates that one or more of the replica shards on the Elasticsearch cluster are not allocated to a node. No...
Read more >[elasticsearch] readiness probe failing at startup when cluster ...
Ok I deleted a pod to test, and it is not starting up with a ready status, the issue is if the cluster...
Read more >K8s Elasticsearch with filebeat is keeping 'not ready' after ...
Issue. There is an issue with elasticsearch readiness probe when running on single replica cluster. Warning Unhealthy 91s (x14 over 3m42s) ...
Read more >Logging OpenShift Container Platform 4.7
The supported way of configuring OpenShift Logging is by configuring it using the ... Check that the Elasticsearch cluster is in a green...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @mtruneck, Thanks for submitting this request, unfortunately we won’t have time to think about it soon so please be patient.
i want this too
i’m running a single node intentionally
yellow
is acceptable for me.