03e7fedb2b
The shutdown script for the elasticsearch-data container uses a trap handler to run the steps outlined in the rolling restart procedure [0]. However, when trying to kill the elasticsearch process (step 3), the script sends the TERM signal to itself. The traps are handled recursively, causing the entire termination grace period to be exhausted before the pod is finally removed. This change updates the trap handler to terminate the child process(es) instead, and wait for their completion. 0: https://www.elastic.co/guide/en/elasticsearch/reference/7.x/restart-cluster.html Change-Id: I0c92ea5cce345cff951f044026a2179dcbd5a3e2 |
||
---|---|---|
.. | ||
bin | ||
monitoring/prometheus | ||
certificates.yaml | ||
configmap-bin-curator.yaml | ||
configmap-bin-elasticsearch.yaml | ||
configmap-etc-curator.yaml | ||
configmap-etc-elasticsearch.yaml | ||
cron-job-curator.yaml | ||
cron-job-verify-repositories.yaml | ||
deployment-client.yaml | ||
deployment-gateway.yaml | ||
ingress-elasticsearch.yaml | ||
job-elasticsearch-template.yaml | ||
job-image-repo-sync.yaml | ||
job-s3-bucket.yaml | ||
job-s3-user.yaml | ||
network-policy.yaml | ||
pod-helm-tests.yaml | ||
secret-elasticsearch.yaml | ||
secret-environment.yaml | ||
secret-ingress-tls.yaml | ||
secret-s3-user.yaml | ||
service-data.yaml | ||
service-discovery.yaml | ||
service-gateway.yaml | ||
service-ingress-elasticsearch.yaml | ||
service-logging.yaml | ||
statefulset-data.yaml | ||
statefulset-master.yaml |