public inbox for [email protected]  

help / color / mirror / Atom feed

From: a venkatesh <[email protected]>
To: [email protected]
To: [email protected]
Subject: pgpool High Availability Issue
Date: Mon, 18 Nov 2019 10:41:12 -0800
Message-ID: <CANLYxgwq-0fOOfdDPPAB9gML45=dqmzFUh=oq-AFTKZcAzRW_w@mail.gmail.com> (raw)

Hi,

I'm working on configuring high availability for pgpool using watchdog.
Initially, I tried with two pgpool nodes (along with a pgmaster and
pgslave). In this scenario, assuming pgpool node 1 was started first and
became the leader. After sometime , the node got disconnected with  pgpool
node 2 and pgpool node 2 as well declared itself as leader.


To handle this kind of scenario, I tried provisioning an additional pgpool
node and made a cluster with total 5 nodes (3 pgpool nodes, 1 pgmaster and
1 pgslave), assuming it will create a quorum to handle such situations.
Unfortunately, the situation still remains the same. (In case of any
disconnection between node that became leader and the first stand by node,
both the nodes try to manage the pgmaster and slave simultaneously).

Please help me understand if this is expected behavior or some additional
configurations are required to be made, so that two pgpool nodes don't
become leader simultaneously.  If it's an expected behavior, how can we
handle this ?

(A point to note is that I'm not using elastic IP address here, instead I
have created a network load balancer in AWS, created a target group with
all the three pgpool nodes as targets).

Regards,

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], [email protected]
  Subject: Re: pgpool High Availability Issue
  In-Reply-To: <CANLYxgwq-0fOOfdDPPAB9gML45=dqmzFUh=oq-AFTKZcAzRW_w@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