By default, the readiness probe checks that the pod can successfully respond to HTTP requests within a three second timeout. This is acceptable in most cases. In some cases (such as when the cluster is under heavy load), it may be helpful to increase the timeout. This allows the pod to stay in a
Ready state and thus be part of the Elasticsearch service even if it is responding slowly. To adjust the timeout, set the
READINESS_PROBE_TIMEOUT environment variable in the pod template. The readiness probe configuration also must be updated with the new timeout. For example, to increase the API call timeout to ten seconds and the overall check time to twelve seconds:
spec: version: 8.6.2 nodeSets: - name: default count: 1 podTemplate: spec: containers: - name: elasticsearch readinessProbe: exec: command: - bash - -c - /mnt/elastic-internal/scripts/readiness-probe-script.sh failureThreshold: 3 initialDelaySeconds: 10 periodSeconds: 12 successThreshold: 1 timeoutSeconds: 12 env: - name: READINESS_PROBE_TIMEOUT value: "10"
Note that this will require restarting the pods.
Intro to Kibana
ELK for Logs & Metrics