c43331d67a
* add preStop hook to trigger Fast Shutdown * disable readiness probe by default When Kubernetes terminates a pod, the container runtime typically sends a SIGTERM signal to pid 1 in each container [0]. PostgreSQL interprets SIGTERM as a request to do a "Smart Shutdown" [1]. This can take minutes (often exhausting the termination grace period), and during this time, new connections are not being serviced. Now that postgresql has a single replica, this behavior is undesirable. If we kill the pod (e.g. in an upgrade), we probably want it to come back as soon as possible. This change adds a preStop hook that sends a SIGINT to postgresql in order to trigger a "Fast Shutdown". In addition, the readiness probe is disabled by default, since it adds no value in a single-replica scenario. 0: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination 1: https://www.postgresql.org/docs/9.6/server-shutdown.html Change-Id: Ib5f3d2a49e55332604c91f9a011e87d78947dbef |
||
---|---|---|
.. | ||
bin | ||
monitoring/prometheus | ||
secrets | ||
configmap-bin.yaml | ||
configmap-etc.yaml | ||
cron-job-backup-postgres.yaml | ||
job-image-repo-sync.yaml | ||
job-ks-user.yaml | ||
network_policy.yaml | ||
pod-test.yaml | ||
postgresql-backup-pvc.yaml | ||
secret-admin.yaml | ||
secret-audit.yaml | ||
secret-backup-restore.yaml | ||
secret-rgw.yaml | ||
secrets-etc.yaml | ||
service-postgres.yaml | ||
service-restapi.yaml | ||
statefulset.yaml |