[pgpool-general: 4505] Re: pgpool unable to attach a node during failback command

Tatsuo Ishii ishii at postgresql.org
Tue Mar 1 17:41:23 JST 2016


You should use online recovery instead of pcp_attach_node.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp

> Hi,
> I have a Hugh problem regarding attaching a node (as secondary) to the pool
> after I performing pcp_attach_node.
> 
> after failover is being completed successfully and valid primary node is
> active, i'm performing an *pcp_attach (via sql)* to the faulty node in
> order to failback as secondary!
> 
> *select pcp_attach_node (0,'10.10.61.99',1200,9898,'*****','*****') *
> 
> during this command, a failback script is being executed and performs the
> following:
> 1. rsync between the DB nodes.
> 2. create recovery.conf.
> 3. startup the node(as secondary).
> 
> *the failback could take for 20 min to finish.*
> 
> after the failback finished *successfully* (exit status 0) and the node
> started as *secondary* (according to postgres) - streaming replication.
> 
> *the pgpool reportes the node status from 1 to 3 (instead of 2).*
> 
> *** when failback finished early (less then few min) the pgpool reports the
> node status as 2 - as aspected.*
> 
> 
> please advice regarding this issue...
> 
> 
> *Thanks,*
> *cohavisi*


More information about the pgpool-general mailing list