Patroni: A Template for PostgreSQL HA with ZooKeeper, etcd or Consul ------------------------------------------------------------There are many ways to run high availability with PostgreSQL; for a list, see the PostgreSQL Documentation.
Patroni is a template for you to create your own customized, high-availability solution using Python and - for maximum accessibility - a distributed configuration store like ZooKeeper, etcd or Consul. Database engineers, DBAs, DevOps engineers, and SREs who are looking to quickly deploy HA PostgreSQL in the datacenter-or anywhere else-will hopefully find it useful.
We call Patroni a "template" because it is far from being a one-size-fits-all or plug-and-play replication system. It will have its own caveats. Use wisely.
Note to Kubernetes users: We're currently developing Patroni to be as useful as possible for teams running Kubernetes on top of Google Compute Engine; Patroni can be the HA solution for Postgres in such an environment. To this end, we've created a Helm Chart that enables you to deploy a five-node Patroni cluster using a Kubernetes PetSet.
| How Patroni Works |
|---|
Patroni originated as a fork of Governor, the project from Compose. It includes plenty of new features. |
For an example of a Docker-based deployment with Patroni, see Spilo, currently in use at Zalando. |
For additional background info, see: |
| * PostgreSQL HA with Kubernetes and Patroni, talk by Josh Berkus at KubeCon 2016 (video) |
| ================ |
| Development Status |
Patroni is in active development and accepts contributions. See our Contributing section below for more details.
We report new releases information here.
| Technical Requirements/Installation |
|---|
For Mac |
To install requirements on a Mac, run the following: |
: |
|
|
| =================== |
| Running and Configuring |
To get started, do the following from different terminals: :
> etcd --data-dir=data/etcd
> ./patroni.py postgres0.yml
> ./patroni.py postgres1.ymlYou will then see a high-availability cluster start up. Test different settings in the YAML files to see how the cluster's behavior changes. Kill some of the components to see how the system behaves.
Add more postgres*.yml files to create an even larger cluster.
Patroni provides an HAProxy configuration, which will give your application a single endpoint for connecting to the cluster's leader. To configure, run:
> haproxy -f haproxy.cfg> psql --host 127.0.0.1 --port 5000 postgres| YAML Configuration |
|---|
Go here for comprehensive information about settings for etcd, consul, and ZooKeeper. And for an example, see postgres0.yml. |
| ========================= |
| Environment Configuration |
Go here for comprehensive information about configuring(overriding) settings via environment variables.
| Replication Choices |
|---|
Patroni uses Postgres' streaming replication, which is asynchronous by default. Patroni's asynchronous replication configuration allows for |
| =============================== |
| Applications Should Not Use Superusers |
When connecting from an application, always use a non-superuser. Patroni requires access to the database to function properly. By using a superuser from an application, you can potentially use the entire connection pool, including the connections reserved for superusers, with the superuser_reserved_connections setting. If Patroni cannot access the Primary because the connection pool is full, behavior will be undesirable.