{"id":15597,"date":"2021-02-03T16:06:46","date_gmt":"2021-02-03T15:06:46","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/"},"modified":"2024-11-08T15:40:13","modified_gmt":"2024-11-08T14:40:13","slug":"postgresql-high-availabilty-patroni-ectd-haproxy-keepalived","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/","title":{"rendered":"PostgreSQL High Availability: Patroni, Ectd , HAProxy , Keepalived"},"content":{"rendered":"

By Mouhamadou Diaw<\/strong><\/p>\n

Patroni<\/a> is one the most famous tool that can be used to setup a high avalaibilty for PostgreSQL. In this blog I am describing a test I did.
\nBelow the environment we will use<\/p>\n

\"\"<\/a>
\nThe etcd cluster will contains 3 servers
\netcd-server1: 192.168.56.100
\netcd-server2: 192.168.56.101
\netcd-server3: 192.168.56.106<\/p>\n

HAProxy and Keepalived will be configured in this 2 servers.
\nhaproxy-server1: 192.168.56.102
\nhaproxy-server2: 192.168.56.103<\/p>\n

A VIP will be configured
\nhaproxyvip 192.168.56.108<\/p>\n

We have 2 databases servers
\npgserver1: 192.168.56.104 (initial primary server)
\npgserver2: 192.168.56.105<\/p>\n

Below a resume of all IP used in this blog<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n<\/td>\n
\n
\n
etcd-server1: 192.168.56.100<\/code><\/div>\n
etcd-server2: 192.168.56.101<\/code><\/div>\n
etcd-server3: 192.168.56.106<\/code><\/div>\n
haproxy-server1: 192.168.56.102<\/code><\/div>\n
haproxy-server2: 192.168.56.103<\/code><\/div>\n
pgserver1: 192.168.56.104<\/code><\/div>\n
pgserver2: 192.168.56.105<\/code><\/div>\n
haproxyvip\u00a0 192.168.56.108<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

All servers are ppc64le architecture. But the steps will not change if you are using X64 architecture
\nEtcd Install<\/strong>
\nThe first steps is to install etcd on all etcd servers
\netcd-server1
\netcd-server2
\netcd-server3<\/p>\n

For the installation of etcd, the latest archive is downloaded here <\/a>
\nThe following steps were done on all 3 etc servers
\nUnpack the etcd downloaded archive<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n<\/td>\n
\n
\n
[root@etcd-server1 ~]<\/code># tar xvzf etcd-v3.4.14-linux-ppc64le.tar.gz<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

And then copy following executables to \/usr\/local\/bin<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n<\/td>\n
\n
\n
[root@etcd-server1 etcd-v3.4.14-linux-ppc64le]<\/code># pwd<\/code><\/div>\n
\/root\/etcd-v3<\/code>.4.14-linux-ppc64le<\/code><\/div>\n
[root@etcd-server1 etcd-v3.4.14-linux-ppc64le]<\/code># cp etcd etcdctl \/usr\/local\/bin\/<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

For the startup a etcd service is created for both servers. This service will contain the configuration values of the etcd cluster.
\nBelow the contents of each service<\/p>\n

-etcd.service etcd-server1<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n<\/td>\n
\n
\n
[root@etcd-server1 ~]<\/code># cat \/etc\/systemd\/system\/etcd.service<\/code><\/div>\n
[Unit]<\/code><\/div>\n
Description=etcd service<\/code><\/div>\n
Documentation=https:<\/code>\/\/github<\/code>.com<\/code>\/coreos\/etcd<\/code><\/div>\n
<\/div>\n
[Service]<\/code><\/div>\n
Type=notify<\/code><\/div>\n
ExecStart=<\/code>\/usr\/local\/bin\/etcd<\/code> --name=etcd0 --data-<\/code>dir<\/code>=<\/code>\/var\/lib\/etcd\/default<\/code>.etcd --initial-advertise-peer-urls=http:<\/code>\/\/192<\/code>.168.56.100:2380 --listen-peer-urls=http:<\/code>\/\/192<\/code>.168.56.100:2380 --listen-client-urls=http:<\/code>\/\/192<\/code>.168.56.100:2379,http:<\/code>\/\/127<\/code>.0.0.1:2379 --advertise-client-urls=http:<\/code>\/\/192<\/code>.168.56.100:2379 --initial-cluster-token=etcd-cluster-1 --initial-cluster=etcd0=http:<\/code>\/\/192<\/code>.168.56.100:2380,etcd1=http:<\/code>\/\/192<\/code>.168.56.101:2380,etcd2=http:<\/code>\/\/192<\/code>.168.56.106:2380 --initial-cluster-state=new<\/code><\/div>\n
Restart=on-failure<\/code><\/div>\n
RestartSec=5<\/code><\/div>\n
[Install]<\/code><\/div>\n
WantedBy=multi-user.target<\/code><\/div>\n
[root@etcd-server1 ~]<\/code>#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

-etcd.service etcd-server2<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n<\/td>\n
\n
\n
[root@etcd-server2 ~]<\/code># cat \/etc\/systemd\/system\/etcd.service<\/code><\/div>\n
Description=etcd service<\/code><\/div>\n
Documentation=https:<\/code>\/\/github<\/code>.com<\/code>\/coreos\/etcd<\/code><\/div>\n
<\/div>\n
[Service]<\/code><\/div>\n
Type=notify<\/code><\/div>\n
ExecStart=<\/code>\/usr\/local\/bin\/etcd<\/code> --name=etcd1 --data-<\/code>dir<\/code>=<\/code>\/var\/lib\/etcd\/default<\/code>.etcd --initial-advertise-peer-urls=http:<\/code>\/\/192<\/code>.168.56.101:2380 --listen-peer-urls=http:<\/code>\/\/192<\/code>.168.56.101:2380 --listen-client-urls=http:<\/code>\/\/192<\/code>.168.56.101:2379,http:<\/code>\/\/127<\/code>.0.0.1:2379 --advertise-client-urls=http:<\/code>\/\/192<\/code>.168.56.101:2379 --initial-cluster-token=etcd-cluster-1 --initial-cluster=etcd0=http:<\/code>\/\/192<\/code>.168.56.100:2380,etcd1=http:<\/code>\/\/192<\/code>.168.56.101:2380,etcd2=http:<\/code>\/\/192<\/code>.168.56.106:2380 --initial-cluster-state=new<\/code><\/div>\n
Restart=on-failure<\/code><\/div>\n
RestartSec=5<\/code><\/div>\n
[Install]<\/code><\/div>\n
WantedBy=multi-user.target<\/code><\/div>\n
[root@etcd-server2 ~]<\/code>#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

-etcd.service etcd-server3<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n<\/td>\n
\n
\n
[root@etcd-server3 ~]<\/code># cat \/etc\/systemd\/system\/etcd.service<\/code><\/div>\n
[Unit]<\/code><\/div>\n
Description=etcd service<\/code><\/div>\n
Documentation=https:<\/code>\/\/github<\/code>.com<\/code>\/coreos\/etcd<\/code><\/div>\n
<\/div>\n
[Service]<\/code><\/div>\n
Type=notify<\/code><\/div>\n
ExecStart=<\/code>\/usr\/local\/bin\/etcd<\/code> --name=etcd2 --data-<\/code>dir<\/code>=<\/code>\/var\/lib\/etcd\/default<\/code>.etcd --initial-advertise-peer-urls=http:<\/code>\/\/192<\/code>.168.56.106:2380 --listen-peer-urls=http:<\/code>\/\/192<\/code>.168.56.106:2380 --listen-client-urls=http:<\/code>\/\/192<\/code>.168.56.106:2379,http:<\/code>\/\/127<\/code>.0.0.1:2379 --advertise-client-urls=http:<\/code>\/\/192<\/code>.168.56.106:2379 --initial-cluster-token=etcd-cluster-1 --initial-cluster=etcd0=http:<\/code>\/\/192<\/code>.168.56.100:2380,etcd1=http:<\/code>\/\/192<\/code>.168.56.101:2380,etcd2=http:<\/code>\/\/192<\/code>.168.56.106:2380 --initial-cluster-state=new<\/code><\/div>\n
Restart=on-failure<\/code><\/div>\n
RestartSec=5<\/code><\/div>\n
[Install]<\/code><\/div>\n
WantedBy=multi-user.target<\/code><\/div>\n
[root@etcd-server3 ~]<\/code>#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Now let\u2019s start etcd services on both servers (stop your firewall or do requested rules)<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n<\/td>\n
\n
\n
[root@etcd-server1 ~]<\/code># systemctl\u00a0 start etcd.service<\/code><\/div>\n
[root@etcd-server2 ~]<\/code># systemctl\u00a0 start etcd.service<\/code><\/div>\n
[root@etcd-server3 ~]<\/code># systemctl\u00a0 start etcd.service<\/code><\/div>\n
[root@etcd-server1 ~]<\/code># systemctl\u00a0 enable etcd.service<\/code><\/div>\n
[root@etcd-server2 ~]<\/code># systemctl\u00a0 enable etcd.service<\/code><\/div>\n
[root@etcd-server3 ~]<\/code># systemctl\u00a0 enable etcd.service<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

If everything is OK, you can query the state of the etcd cluster<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n<\/td>\n
\n
\n
[root@etcd-server2 ~]<\/code># etcdctl endpoint status --cluster -w table<\/code><\/div>\n
+---------------------------+------------------+---------+---------+-----------+------------+-----------+------------+--------------------+--------+<\/code><\/div>\n
|\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ENDPOINT\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ID\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | VERSION | DB SIZE | IS LEADER | IS LEARNER | RAFT TERM | RAFT INDEX | RAFT APPLIED INDEX | ERRORS |<\/code><\/div>\n
+---------------------------+------------------+---------+---------+-----------+------------+-----------+------------+--------------------+--------+<\/code><\/div>\n
| http:<\/code>\/\/192<\/code>.168.56.101:2379 | 56fde5fc4136bc8b |\u00a0 3.4.14 |\u00a0 328 kB |\u00a0\u00a0\u00a0\u00a0 <\/code>false<\/code> |\u00a0\u00a0\u00a0\u00a0\u00a0 <\/code>false<\/code> |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 18 |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 14 |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 14 |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |<\/code><\/div>\n
| http:<\/code>\/\/192<\/code>.168.56.100:2379 |\u00a0 fa26cebd7281c24 |\u00a0 3.4.14 |\u00a0 328 kB |\u00a0\u00a0\u00a0\u00a0 <\/code>false<\/code> |\u00a0\u00a0\u00a0\u00a0\u00a0 <\/code>false<\/code> |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 18 |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 14 |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 14 |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |<\/code><\/div>\n
| http:<\/code>\/\/192<\/code>.168.56.106:2379 | b75652c4850bb9d2 |\u00a0 3.4.14 |\u00a0 328 kB |\u00a0\u00a0\u00a0\u00a0\u00a0 <\/code>true<\/code> |\u00a0\u00a0\u00a0\u00a0\u00a0 <\/code>false<\/code> |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 18 |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 14 |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 14 |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |<\/code><\/div>\n
+---------------------------+------------------+---------+---------+-----------+------------+-----------+------------+--------------------+--------+<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Keepalived and HAProxy Install<\/strong><\/p>\n

These components are installed on following servers
\nhaproxy-server1
\nhaproxy-server2<\/p>\n

To install Keepalived download the latest archive here <\/a>
\nYou will need maybe to install some linux required packages.
\nUnpack the archive and do the configure<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n<\/td>\n
\n
\n
[root@ haproxy-server1\u00a0 ~]<\/code># tar xvzf keepalived-2.2.0.tar.gz<\/code><\/div>\n
[root@ haproxy-server1 ~]<\/code># cd keepalived-2.2.0\/<\/code><\/div>\n
[root@ haproxy-server1 keepalived-2.2.0]<\/code># .\/configure<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

If there is no error then run make and make install<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n<\/td>\n
\n
\n
[root@ haproxy-server1 keepalived-2.2.0]<\/code>#\u00a0 make<\/code><\/div>\n
[root@ haproxy-server1 keepalived-2.2.0]<\/code>#\u00a0 make install<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

For Keepalived startup the same service is created on both servers.<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n<\/td>\n
\n
\n
[root@ haproxy-server1 ~]<\/code># cat \/etc\/systemd\/system\/keepalived.service<\/code><\/div>\n
[Unit]<\/code><\/div>\n
Description=LVS and VRRP High Availability Monitor<\/code><\/div>\n
After=network-online.target syslog.target<\/code><\/div>\n
Wants=network-online.target<\/code><\/div>\n
[Service]<\/code><\/div>\n
Type=forking<\/code><\/div>\n
PIDFile=<\/code>\/run\/keepalived<\/code>.pid<\/code><\/div>\n
KillMode=process<\/code><\/div>\n
EnvironmentFile=-<\/code>\/usr\/local\/etc\/sysconfig\/keepalived<\/code><\/div>\n
ExecStart=<\/code>\/usr\/local\/sbin\/keepalived<\/code> $KEEPALIVED_OPTIONS<\/code><\/div>\n
ExecReload=<\/code>\/bin\/kill<\/code> -HUP $MAINPID<\/code><\/div>\n
[Install]<\/code><\/div>\n
WantedBy=multi-user.target<\/code><\/div>\n
[root@etcd- haproxy-server1 ~]<\/code>#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Before starting keepalived, we have to configure a configuration file on both servers.<\/p>\n

-haproxy-server1<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n
18<\/div>\n
19<\/div>\n
20<\/div>\n
21<\/div>\n
22<\/div>\n
23<\/div>\n
24<\/div>\n
25<\/div>\n<\/td>\n
\n
\n
[root@haproxy-server1 ]<\/code># cat \/etc\/keepalived\/keepalived.conf<\/code><\/div>\n
global_defs {<\/code><\/div>\n
}<\/code><\/div>\n
vrrp_script chk_haproxy { <\/code># Requires keepalived-1.1.13<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>script <\/code>\"killall -0 haproxy\"<\/code> # widely used idiom<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>interval 2 <\/code># check every 2 seconds<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>weight 2 <\/code># add 2 points of prio if OK<\/code><\/div>\n
}<\/code><\/div>\n
vrrp_instance VI_1 {<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>interface eth0<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>state MASTER <\/code># or \"BACKUP\" on backup<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>priority 101 <\/code># 101 on master, 100 on backup<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>virtual_router_id 51<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>authentication {<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>auth_type PASS<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>auth_pass 1234<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>}<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>virtual_ipaddress {<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>192.168.56.108<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>}<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>track_script {<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>chk_haproxy<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>}<\/code><\/div>\n
}<\/code><\/div>\n
[root@haproxy-server1 ]<\/code>#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

-haproxy-server2<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n
18<\/div>\n
19<\/div>\n
20<\/div>\n
21<\/div>\n
22<\/div>\n
23<\/div>\n
24<\/div>\n
25<\/div>\n
26<\/div>\n<\/td>\n
\n
\n
[root@haproxy-server2 ]<\/code># cat \/etc\/keepalived\/keepalived.conf<\/code><\/div>\n
global_defs {<\/code><\/div>\n
}<\/code><\/div>\n
vrrp_script chk_haproxy { <\/code># Requires keepalived-1.1.13<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>script <\/code>\"killall -0 haproxy\"<\/code> # widely used idiom<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>interval 2 <\/code># check every 2 seconds<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>weight 2 <\/code># add 2 points of prio if OK<\/code><\/div>\n
}<\/code><\/div>\n
vrrp_instance VI_1 {<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>interface eth0<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>state BACKUP <\/code># or \"BACKUP\" on backup<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>priority 100 <\/code># 101 on master, 100 on backup<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>virtual_router_id 51<\/code><\/div>\n
<\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>authentication {<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>auth_type PASS<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>auth_pass 1234<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>}<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>virtual_ipaddress {<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>192.168.56.108<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>}<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>track_script {<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>chk_haproxy<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>}<\/code><\/div>\n
}<\/code><\/div>\n
\u00a0<\/code>[root@haproxy-server2 ]<\/code>#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Now it\u2019s time to start Keepalived on both servers can be started on both servers<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n<\/td>\n
\n
\n
[root@haproxy-server1 keepalived]<\/code># systemctl start keepalived<\/code><\/div>\n
[root@haproxy-server1 keepalived]<\/code># systemctl status keepalived<\/code><\/div>\n
[root@haproxy-server1 keepalived]<\/code># systemctl enable keepalived<\/code><\/div>\n
<\/div>\n
[root@haproxy-server2 keepalived]<\/code># systemctl start keepalived<\/code><\/div>\n
[root@haproxy-server2 keepalived]<\/code># systemctl status keepalived<\/code><\/div>\n
[root@haproxy-server2 keepalived]<\/code># systemctl enable keepalived<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

If everything is fine, the VIP 192.168.56.108 should be run on one server and will automatically failover to the the second server if there is any issue with the server.<\/p>\n

Now let’s install the HAProxy on both servers haproxy-server1 and haproxy-server2. We have downloaded the latest HAProxy archive here <\/a><\/p>\n

Then unpack the archive and run the make and make install commands (Maybe you will have to install some linux packages)<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n<\/td>\n
\n
\n
[root@etcd-server2 ~]<\/code># tar xzzf haproxy-2.3.4.tar.gz<\/code><\/div>\n
[root@etcd-server2 ~]<\/code># cd haproxy-2.3.4\/<\/code><\/div>\n
[root@haproxy-server1 haproxy-2.1.5]<\/code># make TARGET=linux-glibc<\/code><\/div>\n
[root@haproxy-server1 haproxy-2.1.5]<\/code># make install<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Following directories are created in my case<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n<\/td>\n
\n
\n
[root@haproxy-server1 haproxy-2.1.5]<\/code>#\u00a0 mkdir -p \/etc\/haproxy<\/code><\/div>\n
[root@haproxy-server1 haproxy-2.1.5]<\/code># mkdir -p \/var\/lib\/haproxy<\/code><\/div>\n
[root@haproxy-server1 haproxy-2.1.5]<\/code># touch \/var\/lib\/haproxy\/stats<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

To startup HAProxy a service is created on both HAProxy servers<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n
18<\/div>\n
19<\/div>\n
20<\/div>\n
21<\/div>\n
22<\/div>\n
23<\/div>\n
24<\/div>\n
25<\/div>\n
26<\/div>\n
27<\/div>\n
28<\/div>\n
29<\/div>\n<\/td>\n
\n
\n
[root@haproxy-server1 system]<\/code># cat haproxy.service<\/code><\/div>\n
<\/div>\n
[Unit]<\/code><\/div>\n
Description=HAProxy Load Balancer<\/code><\/div>\n
Documentation=<\/code>man<\/code>:haproxy(1)<\/code><\/div>\n
Documentation=<\/code>file<\/code>:<\/code>\/usr\/share\/doc\/haproxy\/configuration<\/code>.txt.gz<\/code><\/div>\n
# allows us to do millisecond level restarts without triggering alert in Systemd<\/code><\/div>\n
#StartLimitInterval=0<\/code><\/div>\n
#StartLimitBurst=0<\/code><\/div>\n
After=network.target syslog.service<\/code><\/div>\n
Wants=syslog.service<\/code><\/div>\n
<\/div>\n
[Service]<\/code><\/div>\n
Environment=<\/code>\"CONFIG=\/etc\/haproxy\/haproxy.cfg\"<\/code> \"PIDFILE=\/run\/haproxy.pid\"<\/code><\/div>\n
# EXTRAOPTS and RELOADOPS come from this default file<\/code><\/div>\n
# EnvironmentFile=-\/etc\/default\/haproxy<\/code><\/div>\n
ExecStartPre=<\/code>\/usr\/local\/sbin\/haproxy<\/code> -f $CONFIG -c -q<\/code><\/div>\n
ExecStart=<\/code>\/usr\/local\/sbin\/haproxy<\/code> -W -f $CONFIG -p $PIDFILE $EXTRAOPTS<\/code><\/div>\n
ExecReload=<\/code>\/usr\/local\/sbin\/haproxy<\/code> -f $CONFIG -c -q $EXTRAOPTS $RELOADOPTS<\/code><\/div>\n
ExecReload=<\/code>\/bin\/kill<\/code> -USR2 $MAINPID<\/code><\/div>\n
KillMode=mixed<\/code><\/div>\n
#Restart=always<\/code><\/div>\n
#Type=forking<\/code><\/div>\n
Restart=on-failure<\/code><\/div>\n
RestartSec=5<\/code><\/div>\n
<\/div>\n
[Install]<\/code><\/div>\n
WantedBy=multi-user.target<\/code><\/div>\n
[root@haproxy-server1 system]<\/code>#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

The same haproxy.cfg file is configured on both HAProxy servers like<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n
18<\/div>\n
19<\/div>\n
20<\/div>\n
21<\/div>\n
22<\/div>\n
23<\/div>\n
24<\/div>\n
25<\/div>\n
26<\/div>\n
27<\/div>\n
28<\/div>\n
29<\/div>\n
30<\/div>\n
31<\/div>\n
32<\/div>\n
33<\/div>\n
34<\/div>\n
35<\/div>\n
36<\/div>\n
37<\/div>\n<\/td>\n
\n
\n
[root@haproxy-server1 ]<\/code># cat \/etc\/haproxy\/haproxy.cfg<\/code><\/div>\n
global<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>maxconn 100<\/code><\/div>\n
<\/div>\n
defaults<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>log global<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>mode tcp<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>retries 2<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>timeout client 30m<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>timeout connect 4s<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>timeout server 30m<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>timeout check 5s<\/code><\/div>\n
<\/div>\n
listen stats<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>mode http<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>bind *:7000<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>stats <\/code>enable<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>stats uri \/<\/code><\/div>\n
<\/div>\n
listen production<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>bind 192.168.56.108:5000<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>option httpchk OPTIONS<\/code>\/master<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>http-check expect status 200<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>default-server inter 3s fall 3 rise 2 on-marked-down <\/code>shutdown<\/code>-sessions<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>server postgresql_192.168.56.104_5432 192.168.56.104:5432 maxconn 100 check port 8008<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>server postgresql_192.168.56.105_5432 192.168.56.105:5432 maxconn 100 check port 8008<\/code><\/div>\n
<\/div>\n
listen standby<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>bind 192.168.56.108:5001<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>option httpchk OPTIONS<\/code>\/replica<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>http-check expect status 200<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>default-server inter 3s fall 3 rise 2 on-marked-down <\/code>shutdown<\/code>-sessions<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>server postgresql_192.168.56.104_5432 192.168.56.104:5432 maxconn 100 check port 8008<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>server postgresql_192.168.56.105_5432 192.168.56.105:5432 maxconn 100 check port 8008<\/code><\/div>\n
<\/div>\n
<\/div>\n
[root@haproxy-server1 ]<\/code>#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Let’s start HAProxy<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n<\/td>\n
\n
\n
[root@haproxy-server1 haproxy-2.1.5]<\/code># setsebool -P haproxy_connect_any=1<\/code><\/div>\n
[root@haproxy-server1 system]<\/code># systemctl enable haproxy.service<\/code><\/div>\n
[root@haproxy-server1 system]<\/code># systemctl start haproxy.service<\/code><\/div>\n
[root@haproxy-server1 system]<\/code># systemctl status haproxy.service<\/code><\/div>\n
<\/div>\n
[root@haproxy-server2 system]<\/code># setsebool -P haproxy_connect_any=1<\/code><\/div>\n
[root@haproxy-server2 system]<\/code># systemctl start haproxy.service<\/code><\/div>\n
[root@haproxy-server2 system]<\/code># systemctl status haproxy.service<\/code><\/div>\n
[root@haproxy-server2 system]<\/code># systemctl enable haproxy.service<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Patroni Install<\/strong><\/p>\n

Patroni will be installed on both PostgreQL servers pgserver1 and pgserver2. Some components will be installed with root and some components with the user postgres
\nIn my case I had to install some linux packages<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n<\/td>\n
\n
\n
[root@pgserver1 ~]<\/code># yum install python3-pip.noarch<\/code><\/div>\n
[root@pgserver1 ~]<\/code># yum install python36-devel.x86_64<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

With the user root install following component<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n<\/td>\n
\n
\n
[root@pgserver1 ~]<\/code># pip3 install --upgrade setuptools<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

With the user postgres install these components<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n<\/td>\n
\n
\n
[postgres@pgserver1 ~]$ pip3 <\/code>install<\/code> --user\u00a0 psycopg2-binary<\/code><\/div>\n
[postgres@pgserver1 ~]$ pip3 <\/code>install<\/code> --user\u00a0 python-etcd<\/code><\/div>\n
[postgres@pgserver1 ~]$ pip3 <\/code>install<\/code> --user wheel<\/code><\/div>\n
[postgres@pgserver1 ~]$ pip3 <\/code>install<\/code> --user patroni<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

If all components are installed without error, we can now configure a configuration file for each patroni<\/p>\n

-pgserver1<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n
18<\/div>\n
19<\/div>\n
20<\/div>\n
21<\/div>\n
22<\/div>\n
23<\/div>\n
24<\/div>\n
25<\/div>\n
26<\/div>\n
27<\/div>\n
28<\/div>\n
29<\/div>\n
30<\/div>\n
31<\/div>\n
32<\/div>\n
33<\/div>\n
34<\/div>\n
35<\/div>\n
36<\/div>\n
37<\/div>\n
38<\/div>\n<\/td>\n
\n
\n
[postgres@pgserver1 <\/code>cat<\/code> \/etc\/patroni<\/code>.yaml<\/code><\/div>\n
scope: postgres_poc<\/code><\/div>\n
name: pg-patroni1<\/code><\/div>\n
restapi:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>listen: 192.168.56.104:8008<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>connect_address: 192.168.56.104:8008<\/code><\/div>\n
etcd3:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>hosts: 192.168.56.100:2379,192.168.56.101:2379,192.168.56.106:2379<\/code><\/div>\n
bootstrap:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>dcs:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>ttl: 30<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>loop_wait: 10<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>retry_timeout: 10<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>maximum_lag_on_failover: 1048576<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>postgresql:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>use_pg_rewind: <\/code>true<\/code><\/div>\n
postgresql:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>listen: 192.168.56.104:5432<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>bin_dir: <\/code>\/u01\/app\/postgres\/product\/13\/db_1\/bin<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>connect_address: 192.168.56.104:5432<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>data_dir: <\/code>\/u02\/pgdata<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>pgpass: <\/code>\/tmp\/pgpass<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>authentication:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>replication:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>username: postgres<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>password: postgres<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>superuser:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>username: postgres<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>password: postgres<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>parameters:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>unix_socket_directories: <\/code>'.'<\/code><\/div>\n
tags:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>nofailover: <\/code>false<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>noloadbalance: <\/code>false<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>clonefrom: <\/code>false<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>nosync: <\/code>false<\/code><\/div>\n
<\/div>\n
[postgres@pgserver1 ~]$<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

-pgserver1<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n
18<\/div>\n
19<\/div>\n
20<\/div>\n
21<\/div>\n
22<\/div>\n
23<\/div>\n
24<\/div>\n
25<\/div>\n
26<\/div>\n
27<\/div>\n
28<\/div>\n
29<\/div>\n
30<\/div>\n
31<\/div>\n
32<\/div>\n
33<\/div>\n
34<\/div>\n
35<\/div>\n
36<\/div>\n
37<\/div>\n
38<\/div>\n<\/td>\n
\n
\n
[postgres@pgserver2 ~]$ <\/code>cat<\/code> \/etc\/patroni<\/code>.yaml<\/code><\/div>\n
scope: postgres_poc<\/code><\/div>\n
name: pg-patroni2<\/code><\/div>\n
restapi:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>listen: 192.168.56.105:8008<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>connect_address: 192.168.56.105:8008<\/code><\/div>\n
etcd3:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>hosts: 192.168.56.100:2379,192.168.56.101:2379,192.168.56.106:2379<\/code><\/div>\n
bootstrap:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>dcs:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>ttl: 30<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>loop_wait: 10<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>retry_timeout: 10<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>maximum_lag_on_failover: 1048576<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>postgresql:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>use_pg_rewind: <\/code>true<\/code><\/div>\n
postgresql:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>listen: 192.168.56.105:5432<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>bin_dir: <\/code>\/u01\/app\/postgres\/product\/13\/db_1\/bin<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>connect_address: 192.168.56.105:5432<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>data_dir: <\/code>\/u02\/pgdata<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>pgpass: <\/code>\/tmp\/pgpass<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>authentication:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>replication:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>username: postgres<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>password: postgres<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>superuser:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>username: postgres<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>password: postgres<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>parameters:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>unix_socket_directories: <\/code>'.'<\/code><\/div>\n
tags:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>nofailover: <\/code>false<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>noloadbalance: <\/code>false<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>clonefrom: <\/code>false<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>nosync: <\/code>false<\/code><\/div>\n
<\/div>\n
[postgres@pgserver2 ~]$<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

The pg_hba.conf file should be configured on both databse servers to allow connections from the different servers. Then patroni can be started on both servers.<\/p>\n

On pgserver1 which is actullaly the primary, we will see outputs like<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n<\/td>\n
\n
\n
[postgres@pgserver1 PG1]$ patroni <\/code>\/etc\/patroni<\/code>.yaml<\/code><\/div>\n
\u2026<\/code><\/div>\n
\u2026<\/code><\/div>\n
2020-01-15 20:31:45,898 INFO: acquired session lock as a leader<\/code><\/div>\n
2020-01-15 20:31:55,862 INFO: Lock owner: pg-patroni1; I am pg-patroni1<\/code><\/div>\n
2020-01-15 20:31:55,871 INFO: Lock owner: pg-patroni1; I am pg-patroni1<\/code><\/div>\n
2020-01-15 20:31:55,905 INFO: no action.\u00a0 i am the leader with the lock<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

On pgserver2 which is the standby server we will have outputs like<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n<\/td>\n
\n
\n
[postgres@pgserver2 PG1]$ patroni <\/code>\/etc\/patroni<\/code>.yaml<\/code><\/div>\n
..<\/code><\/div>\n
2020-01-15 20:41:25,941 INFO: Lock owner: pg-patroni1; I am pg-patroni2<\/code><\/div>\n
2020-01-15 20:41:25,941 INFO: does not have lock<\/code><\/div>\n
2020-01-15 20:41:25,952 INFO: no action.\u00a0 i am a secondary and i am following a leader<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

For the automatic startup of Patroni a service can be created on both databases servers<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n
18<\/div>\n
19<\/div>\n<\/td>\n
\n
\n
[root@pgserver1 ~]<\/code># cat \/etc\/systemd\/system\/patroni.service<\/code><\/div>\n
[Service]<\/code><\/div>\n
Type=simple<\/code><\/div>\n
<\/div>\n
User=postgres<\/code><\/div>\n
Group=postgres<\/code><\/div>\n
<\/div>\n
#ExecStart=\/usr\/local\/bin\/patroni \/opt\/patroni\/patroni.yml<\/code><\/div>\n
ExecStart=<\/code>\/home\/postgres\/<\/code>.<\/code>local<\/code>\/bin\/patroni<\/code>\u00a0 \/etc\/patroni<\/code>.yaml<\/code><\/div>\n
<\/div>\n
KillMode=process<\/code><\/div>\n
<\/div>\n
TimeoutSec=30<\/code><\/div>\n
<\/div>\n
Restart=no<\/code><\/div>\n
<\/div>\n
[Install]<\/code><\/div>\n
WantedBy=multi-user.target<\/code><\/div>\n
[root@pgserver1 ~]<\/code>#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

The command patronictl will be used to manage Patroni<\/p>\n

-List the members of the configuration<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n<\/td>\n
\n
\n
[postgres@pgserver1 ~]$ patronictl -c <\/code>\/etc\/patroni<\/code>.yaml list<\/code><\/div>\n
<\/div>\n
+----------+-------------+----------------+--------+---------+----+-----------+<\/code><\/div>\n
| Cluster\u00a0 |\u00a0\u00a0\u00a0 Member\u00a0\u00a0 |\u00a0\u00a0\u00a0\u00a0\u00a0 Host\u00a0\u00a0\u00a0\u00a0\u00a0 |\u00a0 Role\u00a0 |\u00a0 State\u00a0 | TL | Lag <\/code>in<\/code> MB |<\/code><\/div>\n
+----------+-------------+----------------+--------+---------+----+-----------+<\/code><\/div>\n
| postgres | pg-patroni1 | 192.168.56.104 | Leader | running |\u00a0 1 |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |<\/code><\/div>\n
| postgres | pg-patroni2 | 192.168.56.105 | Replica| running |\u00a0 1 |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0 |<\/code><\/div>\n
+----------+-------------+----------------+--------+---------+----+-----------+<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Perform a switchover<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n
18<\/div>\n
19<\/div>\n
20<\/div>\n
21<\/div>\n
22<\/div>\n
23<\/div>\n
24<\/div>\n
25<\/div>\n
26<\/div>\n
27<\/div>\n<\/td>\n
\n
\n
[postgres@pgserver1 ~]$ patronictl -c <\/code>\/etc\/patroni<\/code>.yaml switchover<\/code><\/div>\n
Master [pg-patroni1]:<\/code><\/div>\n
Candidate [<\/code>'pg-patroni2'<\/code>] []:<\/code><\/div>\n
When should the switchover take place (e.g. 2021-01-15T11:16 )\u00a0 [now]:<\/code><\/div>\n
Current cluster topology<\/code><\/div>\n
+ Cluster: postgres_poc (6917537380726361322) ----+----+-----------+<\/code><\/div>\n
| Member\u00a0\u00a0\u00a0\u00a0\u00a0 | Host\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | Role\u00a0\u00a0\u00a0 | State\u00a0\u00a0 | TL | Lag <\/code>in<\/code> MB |<\/code><\/div>\n
+-------------+---------------+---------+---------+----+-----------+<\/code><\/div>\n
| pg-patroni1 | 192.168.56.104| Leader\u00a0 | running |\u00a0 1 |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |<\/code><\/div>\n
| pg-patroni2 | 192.168.56.105| Replica | running |\u00a0 1 |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0 |<\/code><\/div>\n
+-------------+---------------+---------+---------+----+-----------+<\/code><\/div>\n
Are you sure you want to switchover cluster postgres_poc, demoting current master pg-patroni1? [y<\/code>\/N<\/code>]: y<\/code><\/div>\n
2021-01-15 10:16:35.39948 Successfully switched over to <\/code>\"pg-patroni2\"<\/code><\/div>\n
+ Cluster: postgres_poc (6917537380726361322) ----+----+-----------+<\/code><\/div>\n
| Member\u00a0\u00a0\u00a0\u00a0\u00a0 | Host\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | Role\u00a0\u00a0\u00a0 | State\u00a0\u00a0 | TL | Lag <\/code>in<\/code> MB |<\/code><\/div>\n
+-------------+---------------+---------+---------+----+-----------+<\/code><\/div>\n
| pg-patroni1 | 192.168.56.104| Replica | stopped |\u00a0\u00a0\u00a0 |\u00a0\u00a0 unknown |<\/code><\/div>\n
| pg-patroni2 | 192.168.56.105| Leader\u00a0 | running |\u00a0 1 |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |<\/code><\/div>\n
+-------------+---------------+---------+---------+----+-----------+<\/code><\/div>\n
<\/div>\n
[postgres@pgserver1 ~]$ patronictl -c <\/code>\/etc\/patroni<\/code>.yaml list<\/code><\/div>\n
+ Cluster: postgres_poc (6917537380726361322) ----+----+-----------+<\/code><\/div>\n
| Member\u00a0\u00a0\u00a0\u00a0\u00a0 | Host\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | Role\u00a0\u00a0\u00a0 | State\u00a0\u00a0 | TL | Lag <\/code>in<\/code> MB |<\/code><\/div>\n
+-------------+---------------+---------+---------+----+-----------+<\/code><\/div>\n
| pg-patroni1 | 192.168.56.104| Replica | running |\u00a0 2 |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0 |<\/code><\/div>\n
| pg-patroni2 | 192.168.56.105| Leader\u00a0 | running |\u00a0 2 |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |<\/code><\/div>\n
+-------------+---------------+---------+---------+----+-----------+<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

If the primary crash, the replica will be automatically promoted.
\nFor the connection to the databases, client can use the VIP configured via HAProxy<\/p>\n

-To connect to the standby the port 5001 is used<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n<\/td>\n
\n
\n
[postgres@ [~]> psql -h 192.168.56.108 -p 5001 -U postgres<\/code><\/div>\n
Password <\/code>for<\/code> user postgres:<\/code><\/div>\n
psql (13.1)<\/code><\/div>\n
SSL connection (protocol: TLSv1.2, cipher: ECDHE-RSA-AES256-GCM-SHA384, bits: 256, compression: off)<\/code><\/div>\n
Type <\/code>\"help\"<\/code> for<\/code> help.<\/code><\/div>\n
postgres=<\/code># select pg_is_in_recovery();<\/code><\/div>\n
\u00a0<\/code>pg_is_in_recovery<\/code><\/div>\n
-------------------<\/code><\/div>\n
\u00a0<\/code>t<\/code><\/div>\n
(1 row)<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

-To connect to the primary the port 5000 is used<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n<\/td>\n
\n
\n
[postgres@ [~]> psql -h 192.168.56.108 -p 5000 -U postgres<\/code><\/div>\n
Password <\/code>for<\/code> user postgres:<\/code><\/div>\n
psql (13.1)<\/code><\/div>\n
SSL connection (protocol: TLSv1.2, cipher: ECDHE-RSA-AES256-GCM-SHA384, bits: 256, compression: off)<\/code><\/div>\n
Type <\/code>\"help\"<\/code> for<\/code> help.<\/code><\/div>\n
postgres=<\/code># select pg_is_in_recovery();<\/code><\/div>\n
\u00a0<\/code>pg_is_in_recovery<\/code><\/div>\n
-------------------<\/code><\/div>\n
\u00a0<\/code>f<\/code><\/div>\n
(1 row)<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Conclusion<\/h3>\n

Hope this may help<\/p>\n","protected":false},"excerpt":{"rendered":"

By Mouhamadou Diaw Patroni is one the most famous tool that can be used to setup a high avalaibilty for PostgreSQL. In this blog I am describing a test I did. Below the environment we will use The etcd cluster will contains 3 servers etcd-server1: 192.168.56.100 etcd-server2: 192.168.56.101 etcd-server3: 192.168.56.106 HAProxy and Keepalived will be […]<\/p>\n","protected":false},"author":28,"featured_media":15599,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229,198,83],"tags":[1618,1348,1825,1543,2245],"type_dbi":[],"class_list":["post-15597","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-database-administration-monitoring","category-database-management","category-postgresql","tag-etcd","tag-haproxy","tag-keep-alive","tag-patroni","tag-postgresql-13"],"acf":[],"yoast_head":"\nPostgreSQL High Availability: Patroni, Ectd , HAProxy , Keepalived - dbi Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"PostgreSQL High Availability: Patroni, Ectd , HAProxy , Keepalived\" \/>\n<meta property=\"og:description\" content=\"By Mouhamadou Diaw Patroni is one the most famous tool that can be used to setup a high avalaibilty for PostgreSQL. In this blog I am describing a test I did. Below the environment we will use The etcd cluster will contains 3 servers etcd-server1: 192.168.56.100 etcd-server2: 192.168.56.101 etcd-server3: 192.168.56.106 HAProxy and Keepalived will be […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2021-02-03T15:06:46+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2024-11-08T14:40:13+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/Picture1-8.png\" \/>\n\t<meta property=\"og:image:width\" content=\"591\" \/>\n\t<meta property=\"og:image:height\" content=\"309\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Open source Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Open source Team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"11 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/\"},\"author\":{\"name\":\"Open source Team\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/59554f0d99383431eb6ed427e338952b\"},\"headline\":\"PostgreSQL High Availability: Patroni, Ectd , HAProxy , Keepalived\",\"datePublished\":\"2021-02-03T15:06:46+00:00\",\"dateModified\":\"2024-11-08T14:40:13+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/\"},\"wordCount\":619,\"commentCount\":1,\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/Picture1-8.png\",\"keywords\":[\"etcd\",\"HAProxy\",\"keep-alive\",\"Patroni\",\"PostgreSQL 13\"],\"articleSection\":[\"Database Administration & Monitoring\",\"Database management\",\"PostgreSQL\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/\",\"name\":\"PostgreSQL High Availability: Patroni, Ectd , HAProxy , Keepalived - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/Picture1-8.png\",\"datePublished\":\"2021-02-03T15:06:46+00:00\",\"dateModified\":\"2024-11-08T14:40:13+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/59554f0d99383431eb6ed427e338952b\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/#primaryimage\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/Picture1-8.png\",\"contentUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/Picture1-8.png\",\"width\":591,\"height\":309},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"PostgreSQL High Availability: Patroni, Ectd , HAProxy , Keepalived\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/59554f0d99383431eb6ed427e338952b\",\"name\":\"Open source Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g\",\"caption\":\"Open source Team\"},\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/open-source-team\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"PostgreSQL High Availability: Patroni, Ectd , HAProxy , Keepalived - dbi Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/","og_locale":"en_US","og_type":"article","og_title":"PostgreSQL High Availability: Patroni, Ectd , HAProxy , Keepalived","og_description":"By Mouhamadou Diaw Patroni is one the most famous tool that can be used to setup a high avalaibilty for PostgreSQL. In this blog I am describing a test I did. Below the environment we will use The etcd cluster will contains 3 servers etcd-server1: 192.168.56.100 etcd-server2: 192.168.56.101 etcd-server3: 192.168.56.106 HAProxy and Keepalived will be […]","og_url":"https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/","og_site_name":"dbi Blog","article_published_time":"2021-02-03T15:06:46+00:00","article_modified_time":"2024-11-08T14:40:13+00:00","og_image":[{"width":591,"height":309,"url":"http:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/Picture1-8.png","type":"image\/png"}],"author":"Open source Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Open source Team","Est. reading time":"11 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/"},"author":{"name":"Open source Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/59554f0d99383431eb6ed427e338952b"},"headline":"PostgreSQL High Availability: Patroni, Ectd , HAProxy , Keepalived","datePublished":"2021-02-03T15:06:46+00:00","dateModified":"2024-11-08T14:40:13+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/"},"wordCount":619,"commentCount":1,"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/Picture1-8.png","keywords":["etcd","HAProxy","keep-alive","Patroni","PostgreSQL 13"],"articleSection":["Database Administration & Monitoring","Database management","PostgreSQL"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/","url":"https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/","name":"PostgreSQL High Availability: Patroni, Ectd , HAProxy , Keepalived - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/#primaryimage"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/Picture1-8.png","datePublished":"2021-02-03T15:06:46+00:00","dateModified":"2024-11-08T14:40:13+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/59554f0d99383431eb6ed427e338952b"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/#primaryimage","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/Picture1-8.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/Picture1-8.png","width":591,"height":309},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-high-availabilty-patroni-ectd-haproxy-keepalived\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"PostgreSQL High Availability: Patroni, Ectd , HAProxy , Keepalived"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/59554f0d99383431eb6ed427e338952b","name":"Open source Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g","caption":"Open source Team"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/open-source-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/15597","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/28"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=15597"}],"version-history":[{"count":1,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/15597\/revisions"}],"predecessor-version":[{"id":26130,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/15597\/revisions\/26130"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media\/15599"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=15597"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=15597"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=15597"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=15597"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}