- Elastic Cloud on Kubernetes:
- Overview
- Quickstart
- Upgrading the Elastic Stack version
- Deploying ECK on OpenShift
- Accessing Elastic Stack services
- Managing compute resources
- Running Elasticsearch on ECK
- Pod Template
- JVM heap size
- Node configuration
- Volume claim templates
- HTTP settings & TLS SANs
- Virtual memory
- Custom HTTP certificate
- Settings managed by ECK
- Secure settings
- Custom configuration files and plugins
- Init containers for plugin downloads
- Update strategy
- Pod disruption budget
- Nodes orchestration
- Advanced Elasticsearch node scheduling
- Create automated snapshots
- Readiness probe
- Pod PreStop hook
- Running Kibana on ECK
- Running APM Server on ECK
- Creating custom images
- Configuring ECK
- Service meshes
- Managing licenses in ECK
- Troubleshooting
- Upgrading ECK
- Uninstalling ECK
- Glossary
- API Reference
- Release highlights
- Release notes
Readiness probe
editReadiness probe
editBy 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.17.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.