[pgpool-general: 5224] Re: Node status mismatch on primary/secondary (status 0?)
Tatsuo Ishii
ishii at sraoss.co.jp
Wed Jan 11 18:00:17 JST 2017
> PGPool-II 3.5.4, streaming replication mode. Everything seems to be working correctly - Postgres replicating properly, standby not behind primary, no errors in either PGPool or Postgres logs, on either primary or standby.
>
> The primary reports:
>
> => show pool_nodes;
> node_id | hostname | port | status | lb_weight | role | select_cnt
> ---------+--------------+------+--------+-----------+---------+------------
> 0 | host0 | 5433 | 2 | 0.500000 | primary | 4183
> 1 | host1 | 5433 | 0 | 0.500000 | standby | 0
> (2 rows)
>
>
> The secondary reports:
>
> => show pool_nodes;
> node_id | hostname | port | status | lb_weight | role | select_cnt
> ---------+--------------+------+--------+-----------+---------+------------
> 0 | host0 | 5433 | 2 | 0.500000 | primary | 8
> 1 | host1 | 5433 | 2 | 0.500000 | standby | 0
> (2 rows)
>
>
> I've tried restarting (both nodes), deleting the status file(s), reconfiguring, and several other things, but no matter what I do, the primary reports that node 1 is in status 0.
> Why does this happen, and what can I do to fix it?
It is likely there's something wrong with pgpool.conf entry for host1
on the primary server.
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
More information about the pgpool-general
mailing list