Initial setup for high availability¶

This guide provides instructions on how to set up a highly available PostgreSQL cluster with Patroni. This guide relies on the provided architecture for high-availability.

Considerations¶

This is an example deployment where etcd runs on the same host machines as the Patroni and PostgreSQL and there is a single dedicated HAProxy host. Alternatively etcd can run on different set of nodes.

If etcd is deployed on the same host machine as Patroni and PostgreSQL, separate disk system for etcd and PostgreSQL is recommended due to performance reasons.

For this setup, we will use the nodes that have the following IP addresses:

Node name	Public IP address	Internal IP address
node1	157.230.42.174	10.104.0.7
node2	68.183.177.183	10.104.0.2
node3	165.22.62.167	10.104.0.8
HAProxy1	112.209.126.159	10.104.0.6
HAProxy2	134.209.111.138	10.104.0.5
HAProxy3	134.60.204.27	10.104.0.3
backup	97.78.129.11	10.104.0.9

Important

We recommend not to expose the hosts/nodes where Patroni / etcd / PostgreSQL are running to public networks due to security risks. Use Firewalls, Virtual networks, subnets or the like to protect the database hosts from any kind of attack.

Configure name resolution¶

It’s not necessary to have name resolution, but it makes the whole setup more readable and less error prone. Here, instead of configuring a DNS, we use a local name resolution by updating the file /etc/hosts. By resolving their hostnames to their IP addresses, we make the nodes aware of each other’s names and allow their seamless communication.

Run the following commands on each node.

Set the hostname for nodes. Change the node name to node1, node2, node3, HAProxy1, HAProxy2 and backup, respectively:
```
$ sudo hostnamectl set-hostname node1
```

Modify the /etc/hosts file of each node to include the hostnames and IP addresses of the remaining nodes. Add the following at the end of the /etc/hosts file on all nodes:

# Cluster IP and names

10.104.0.7 node1    
10.104.0.2 node2    
10.104.0.8 node3    
10.104.0.6 HAProxy1 
10.104.0.5 HAProxy2 
10.104.0.3 HAProxy3
10.104.0.9 backup

Configure Percona repository¶

To install the software from Percona, you need to subscribe to Percona repositories. To do this, you require percona-release - the repository management tool.

Run the following commands on each node as the root user or with sudo privileges.

Install percona-release
On Debian and Ubuntu On RHEL and derivatives
1. Install the curl download utility if it’s not installed already:
  
  $ sudo apt update $ sudo apt install curl
2. Download the percona-release repository package:
  
  $ curl -O https://repo.percona.com/apt/percona-release_latest.generic_all.deb
3. Install the downloaded repository package and its dependencies using apt:
  
  $ sudo apt install gnupg2 lsb-release ./percona-release_latest.generic_all.deb
4. Refresh the local cache to update the package information:
  
  $ sudo apt update
Run the following command as the root user or with sudo privileges:
$ sudo yum install -y https://repo.percona.com/yum/percona-release-latest.noarch.rpm
Enable the repository:
```
$ sudo percona-release setup ppg17 
```

Next steps¶

Install Percona Distribution for PostgreSQL

Get expert help¶

If you need assistance, visit the community forum for comprehensive and free database knowledge, or contact our Percona Database Experts for professional support and services.

Community Forum Get a Percona Expert Join Percona Squad