public inbox for [email protected]  

help / color / mirror / Atom feed

From: Pratik Pandit <[email protected]>
To: [email protected]
Subject: Best practices for a 2-node Patroni + PostgreSQL cluster with a external/witness DCS
Date: Wed, 3 Jun 2026 23:50:27 +0530
Message-ID: <CAFchsDX8Wt9Emwx1ESYSx0x+w7GZYLu=mjh3QfNRxcWe9kKR6A@mail.gmail.com> (raw)

Hello PostgreSQL Community,

I am planning to set up a high-availability PostgreSQL cluster using
Patroni. Due to infrastructure constraints, I only have two dedicated
database nodes available.
I know that a Distributed Configuration Store (like etcd or Consul)
requires an odd number of nodes (minimum 3) to achieve quorum and safely
prevent split-brain scenarios.

Before I begin the deployment, I would appreciate your advice on the
following architectural approaches:
 1. Is it recommended to run a 3-node etcd cluster where 2 instances live
on the DB nodes and a 3rd "witness" instance lives on a lightweight
application server/VM?
2. Alternatively, does Patroni safely support a 2-node setup using a single
external DCS instance, or does that introduce a critical single point of
failure (SPOF)?

Any architectural pointers or template configurations for this constraint
would be highly appreciated.
Thanks!

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Best practices for a 2-node Patroni + PostgreSQL cluster with a external/witness DCS
  In-Reply-To: <CAFchsDX8Wt9Emwx1ESYSx0x+w7GZYLu=mjh3QfNRxcWe9kKR6A@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox