pgpool High Availability Issue

From: a venkatesh <venkatesh(dot)sasi(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: pgpool High Availability Issue
Date: 2019-11-15 19:04:22
Message-ID: CANLYxgw4o7sKrMAWZd1o1ZERaXs_hXK4O5ctc0XTkSsFhWMzcw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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,
Venkatesh.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Pavel Stehule 2019-11-15 19:14:17 Re: jsonb_set() strictness considered harmful to data
Previous Message John Lumby 2019-11-15 18:37:25 access to original-statement predicates in an INSTEAD-OF row trigger