Readiness probe

By default, the readiness probe checks that the Pod responds to HTTP requests within a timeout of three seconds. This is acceptable in most cases. However, when the cluster is under heavy load, you might need to increase the timeout. This allows the Pod to stay in a Ready state and 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 and update the readiness probe configuration with the new timeout.

This example describes how to increase the API call timeout to ten seconds and the overall check time to twelve seconds:

spec:
  version: 8.15.3
  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 requires restarting the Pods.

We do not recommend overriding the default readiness probe on Elasticsearch 8.2.0 and later. ECK configures a socket based readiness probe using the Elasticsearch readiness port feature which is not influenced by the load on the Elasticsearch cluster.