[pgpool-general: 8348] Re: is possible pgpool-II 4.3.x with only 2 nodes and VIP address?
Bo Peng
pengbo at sraoss.co.jp
Mon Jul 25 21:38:00 JST 2022
Hello,
> I think for lost of quorum, but i didnt find right setting and parameter to
> get it work. Is it possible? I know that 2 nodes solution have some
> limition, like split brain in rare case etc.
If only one pgpool node is running, the VIP will not be assigned
unless you turn on "enable_consensus_with_half_votes".
[enable_consensus_with_half_votes]
https://www.pgpool.net/docs/latest/ja/html/runtime-watchdog-config.html#GUC-ENABLE-CONSENSUS-WITH-HALF-VOTES
> should someone confirm me, if is possible to setup configuration with
> pgpool-II 4.3.x , pgsql 14.x with just 2 nodes and VIP address?
>
> Each node will have a pgpool-II role, and pgsql 14.x role. I have experience
> with 2 nodes setting with pgpool-II 3.x and psql 11/10/9.
>
>
>
>
> When I trying to set it up, pgpool always relase delagate IP address, when
> node B is powered off or service pgpool stopped.
>
>
> I think for lost of quorum, but i didnt find right setting and parameter to
> get it work. Is it possible? I know that 2 nodes solution have some
> limition, like split brain in rare case etc.
>
>
>
>
>
> Thank you for reply and have nice day
>
>
>
>
> - JEM
>
>
>
>
>
> examples of pgpool-II log
>
>
>
>
> 22-07-21 15:17:18: pid 2023084:LOG: new IPC connection received
> 2022-07-21 15:17:24: pid 2023084:LOG: read from socket failed, remote end
> closed the connection
> 2022-07-21 15:17:24: pid 2023084:LOG: client socket of a.a.b.b:5433 Linux
> node-b.local is closed
> 2022-07-21 15:17:24: pid 2023084:LOG: remote node "a.a.b.b:5433 Linux node-
> b.local" is shutting down
> 2022-07-21 15:17:24: pid 2023084:LOG: removing watchdog node "a.a.b.b:5433
> Linux node-b.local" from the standby list
> 2022-07-21 15:17:24: pid 2023084:LOG: We have lost the quorum
> 2022-07-21 15:17:24: pid 2023084:LOG: signal_user1_to_parent_with_reason(3)
> 2022-07-21 15:17:24: pid 2023081:LOG: Pgpool-II parent process received
> SIGUSR1
> 2022-07-21 15:17:24: pid 2023081:LOG: Pgpool-II parent process received
> watchdog quorum change signal from watchdog
> 2022-07-21 15:17:24: pid 2030089:LOG: watchdog: de-escalation started
> 2022-07-21 15:17:24: pid 2023084:LOG: new IPC connection received
> 2022-07-21 15:17:24: pid 2030089:LOG: successfully released the delegate
> IP:"x.x.x.x"
> 2022-07-21 15:17:24: pid 2030089:DETAIL: 'if_down_cmd' returned with
> success
> 2022-07-21 15:17:24: pid 2023084:LOG: watchdog de-escalation process with
> pid: 2030089 exit with SUCCESS.
> 2022-07-21 15:17:25: pid 2023081:LOG: child process with pid: 2028676 exits
> with sta
--
Bo Peng <pengbo at sraoss.co.jp>
SRA OSS, Inc. Japan
https://www.sraoss.co.jp/
More information about the pgpool-general
mailing list