[pgpool-general: 6001] Re: pgpool 3.7.2 status mismatch between show nodes and node info?
Bo Peng
pengbo at sraoss.co.jp
Thu Mar 15 15:36:16 JST 2018
Hi,
Did failover happened or tried online recovery?
Could you give more info about that what happened before got this stat?
On Wed, 7 Mar 2018 07:43:26 +0100 (CET)
Daniel Westermann <daniel.westermann at dbi-services.com> wrote:
> Hi,
>
> I have a strange behavior with pgpool 3.7.2 and I can't figure out where it is coming from. This is the situation:
>
> I have three nodes with watchdog configuration:
>
> 192.168.22.34: pgpool + postgres
> 192.168.22.35: pgpool + postgres
> 192.168.22.36: pgpool
>
>
> The current status:
>
> postgres at pgpool2:/home/postgres/ [PG1] alias pgpshownodes
> alias pgpshownodes='psql -h ${PGPOOLNODEVIP} -p ${PGPOOLNODEPORT} -f ${DMK_HOME}/sql/show_pgp_nodes.sql postgres'
> postgres at pgpool2:/home/postgres/ [PG1] pgpshownodes
> node_id | hostname | port | status | lb_weight | role | select_cnt | load_balance_node | replicatio
> ---------+---------------+------+--------+-----------+---------+------------+-------------------+-----------
> 0 | 192.168.22.34 | 5433 | up | 0.500000 | standby | 0 | false | 0
> 1 | 192.168.22.35 | 5433 | up | 0.500000 | primary | 0 | true | 0
> (2 rows)
>
> Why does pcp_node_info show both instances as standby?
>
> postgres at pgpool2:/home/postgres/ [PG1] alias pgpnodeinfo
> alias pgpnodeinfo='${PGPOOLHOME}/bin/pcp_node_info -h ${DMK_HOME}/tmp/ -w'
> postgres at pgpool2:/home/postgres/ [PG1] pgpnodeinfo -n 1 --verbose
> Hostname : 192.168.22.35
> Port : 5433
> Status : 1
> Weight : 0.500000
> Status Name: waiting
> Role : standby
> postgres at pgpool2:/home/postgres/ [PG1] pgpnodeinfo -n 0 --verbose
> Hostname : 192.168.22.34
> Port : 5433
> Status : 1
> Weight : 0.500000
> Status Name: waiting
> Role : standby
>
> Any hints appreciated.
> Regards
> Daniel
>
--
Bo Peng <pengbo at sraoss.co.jp>
SRA OSS, Inc. Japan
More information about the pgpool-general
mailing list