pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jehan-Guillaume de Rorthais <jgdr@dalibo.com>
To: Tatsuo Ishii <ishii@sraoss.co.jp>
Cc: inzamam.shafiq@hotmail.com
Cc: cyberdemn@gmail.com
Cc: pgsql-general@lists.postgresql.org
Subject: Re: Patroni vs pgpool II
Date: Thu, 6 Apr 2023 17:41:58 +0200
Message-ID: <20230406174158.62c47a30@karst> (raw)
In-Reply-To: <20230405.165015.9256683667589504.t-ishii@sranhm.sra.co.jp>
References: <CAFh8B=m5dhaozOzGrduqw3jQ5ML8-sVtM6+P9Lc-Bu6rmHsNAQ@mail.gmail.com>
	<20230405.163826.1094418722086264919.t-ishii@sranhm.sra.co.jp>
	<AM9P251MB03305BE93D8FBFA4F481357498909@AM9P251MB0330.EURP251.PROD.OUTLOOK.COM>
	<20230405.165015.9256683667589504.t-ishii@sranhm.sra.co.jp>

On Wed, 05 Apr 2023 16:50:15 +0900 (JST)
Tatsuo Ishii <ishii@sraoss.co.jp> wrote:

> > But, I heard PgPool is still affected by Split brain syndrome.  
> 
> Can you elaborate more? If more than 3 pgpool watchdog nodes (the
> number of nodes must be odd) are configured, a split brain can be
> avoided.

Split brain is a hard situation to avoid. I suppose OP is talking about
PostgreSQL split brain situation. I'm not sure how PgPool's watchdog would
avoid that.

To avoid split brain, you need to implement a combinaison of quorum and
(self-)fencing.

Patroni quorum is in the DCS's hands. Patroni's self-fencing can be achieved
with the (hardware) watchdog. You can also implement node fencing through the
"pre_promote" script to fence the old primary node before promoting the new one.

If you need HA with a high level of anti-split-brain security, you'll not be
able to avoid some sort of fencing, no matter what.

Good luck.





view thread (24+ messages)  latest in thread

Message-ID: <20230406174158.62c47a30@karst>
Permalink:  ../20230406174158.62c47a30@karst/
Also on:    postgresql.org/message-id/20230406174158.62c47a30@karst

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: jgdr@dalibo.com, ishii@sraoss.co.jp, inzamam.shafiq@hotmail.com, cyberdemn@gmail.com
  Subject: Re: Patroni vs pgpool II
  In-Reply-To: <20230406174158.62c47a30@karst>
  References: <CAFh8B=m5dhaozOzGrduqw3jQ5ML8-sVtM6+P9Lc-Bu6rmHsNAQ@mail.gmail.com> <20230405.163826.1094418722086264919.t-ishii@sranhm.sra.co.jp> <AM9P251MB03305BE93D8FBFA4F481357498909@AM9P251MB0330.EURP251.PROD.OUTLOOK.COM> <20230405.165015.9256683667589504.t-ishii@sranhm.sra.co.jp> <20230406174158.62c47a30@karst>

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

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