How to change Elasticsearch pod readiness probe timeout period
Issue
- Our Elasticsearch pods in openshift-logging project are not starting up because of the failing readiness probe.
- This behaviour can be:
- permanent (pods will not ever start)
- temporary (need to restart pods multiple times to make them start properly)
-
We are seeing following error messages:
Timed out waiting for Elasticsearch to be ready HTTP/1.1 503 Service Unavailable
Environment
- Red Hat OpenShift Container Platform (OpenShift) 3.11
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.