Alexander Kukushkin
e2faf641d5
Also governor is able to pick up already running master and slave instances without restarting them. In case is you have a lock and postgres is not running behaviour remains the same: it will start master in read only mode and then promote if it still has the lock.
Governor: A Template for PostgreSQL HA with etcd
There are many ways to run high availability with PostgreSQL; here we present a template for you to create your own custom fit high availability solution using etcd and python for maximum accessibility.
Compose runs a a Postgresql as a service platform, which is highly-available from creation. This is a coded example from our prior blog post: High Availability for PostgreSQL, Batteries Not Included.
Getting Started
To get started, do the following from different terminals:
> etcd --data-dir=data/etcd
> ./governor.py postgres0.yml
> ./governor.py postgres1.yml
From there, you will see a high-availability cluster start up. Test different settings in the YAML files to see how behavior changes. Kill some of the different components to see how the system behaves.
Add more postgres*.yml files to create an even larger cluster.
We provide a haproxy configuration, which will give your application a single endpoint for connecting to the cluster's leader. To configure, run:
> haproxy -f haproxy.cfg
> sh haproxy_status.sh 127.0.0.1 5432 15432
> sh haproxy_status.sh 127.0.0.1 5433 15433
> psql --host 127.0.0.1 --port 5000 postgres
How Governor works
For a diagram of the high availability decision loop, see the included a PDF: postgres-ha.pdf
Requirements on a Mac
Run the following on a Mac to install requirements:
brew install postgresql etcd haproxy libyaml python
pip install psycopg2 pyyaml
Notice
There are many different ways to do HA with PostgreSQL, see the PostgreSQL documentation for a complete list.
We call this project a "template" because it is far from a one-size fits all, or a plug-and-play replication system. It will have it's own caveats. Use wisely.