[pgpool-general: 6672] Query

Lakshmi Raghavendra lakshmiym108 at gmail.com
Sat Aug 17 02:25:09 JST 2019


Hi Pgpool Team,

              *We are nearing a production release and running into the
below issues.*
Replies at the earliest would be highly helpful and greatly appreciated.
Please let us know on how to get rid of the below issues.

We have a 3 node pgpool + postgres cluster - M1 , M2, M3. The pgpool.conf
is as attached.

*Case I :  *
M1 - Pgpool Master + Postgres Master
M2 , M3 - Pgpool slave + Postgres slave

- M1 goes out of network. its marked as LOST in the pgpool cluster
- M2 becomes postgres master
- M3 becomes pgpool master.
- When M1 comes back to the network, pgpool is able to solve split brain.
However, its changing the postgres master back to M1 by logging a statement
- "LOG:  primary node was chenged after the sync from new master", so since
M2 was already postgres master (and its trigger file is not touched) its
not able to sync to the new master.
*I somehow want to avoid this postgres master change..please let us know if
there is a way to avoid it*


*Case II:*

M1 - Pgpool Master + Postgres Master
M2 , M3 - Pgpool slave + Postgres slave

- Shut down M1, M2
- M3 is rightly elected as the pgpool master.
- However when failover request kicks in, the watchdog rejects with the
below log .* Is there a way to make M3 as the postgres master, inspite of
the quorum ?*
*Please let me know.*


2019-08-16T11:15:04+00:00 lcm-34-182 pgpool[11002]: [92-1] 2019-08-16
11:15:04: pid 11002: LOG: watchdog is processing the failover command
[DEGENERATE_BACKEND_REQUEST] received from local pgpool-II on IPC interface
2019-08-16T11:15:04+00:00 lcm-34-182 pgpool[11002]: [93-1] 2019-08-16
11:15:04: pid 11002: LOG: failover requires the quorum to hold, which is
not present at the moment
2019-08-16T11:15:04+00:00 lcm-34-182 pgpool[11002]: [93-2] 2019-08-16
11:15:04: pid 11002: DETAIL: Rejecting the failover request
2019-08-16T11:15:04+00:00 lcm-34-182 pgpool[11002]: [94-1] 2019-08-16
11:15:04: pid 11002: LOG: failover command [DEGENERATE_BACKEND_REQUEST]
request from pgpool-II node "lcm-34-182.dev.lcm.local:9999 Linux
lcm-34-182.dev.lcm.local" is rejected because the watchdog cluster does not
hold the quorum
2019-08-16T11:15:04+00:00 lcm-34-182 pgpool[11049]: [23-1] 2019-08-16
11:15:04: pid 11049: LOG: degenerate backend request for 1 node(s) from pid
[11049], is changed to quarantine node request by watchdog


Please let me know the solutions at the earliest, awaiting for a reply.

Thanks in Advance !!!
Lakshmi Y M
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20190816/97b0392a/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pgpool.conf
Type: application/octet-stream
Size: 40934 bytes
Desc: not available
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20190816/97b0392a/attachment-0001.obj>


More information about the pgpool-general mailing list