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