Phil Sphicas
c43331d67a
postgresql: Optimize restart behavior
* 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
Openstack-Helm-Infra
Mission
The goal of OpenStack-Helm-Infra is to provide charts for services or integration of third-party solutions that are required to run OpenStack-Helm.
For more information, please refer to the OpenStack-Helm repository.
Communication
- Join us on IRC: #openstack-helm on freenode
- Community IRC Meetings: [Every Tuesday @ 3PM UTC], #openstack-meeting-alt on freenode
- Meeting Agenda Items: Agenda
- Join us on Slack
- #openstack-helm
Contributing
We welcome contributions. Check out this document if you would like to get involved.
Description
Languages
Smarty
86.1%
Shell
12.1%
Python
1.3%
Jinja
0.3%
Makefile
0.2%