<div dir="ltr">OK....Thanks!<div><br><div>I'm trying to implement an failover/failback on the nodes:</div><div>1. primary node gets down.</div><div>2. pgpool promotes the secondary node - make it primary.</div><div>3. by attaching the failed node (old primary) - the failback.sh is called and recovering the failed node (using rsync - much more faster) and make it online secondary! </div><div><div><div><br></div><div>from what you are saying...<br><div>just to make sure, I <b>can not</b> use the failback.sh script (which called by pcp_attach_node) in order "recover" the node and make it online (as scondary).</div></div></div></div><div><br></div><div><br></div><div>Thanks,</div><div>cohavisi</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Mar 1, 2016 at 2:15 PM, Tatsuo Ishii <span dir="ltr"><<a href="mailto:ishii@postgresql.org" target="_blank">ishii@postgresql.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'm not sure what you want to do (especialy I'm confused by<br>
"secondary": what does it mean?). Have you taken look at follow master<br>
script?<br>
<br>
Anyway...<br>
<br>
pcp_attach_node should be used for the case PostgreSQL server is<br>
online and ready to use. Not for recovering a PostgreSQL server.<br>
<div class="HOEnZb"><div class="h5"><br>
Best regards,<br>
--<br>
Tatsuo Ishii<br>
SRA OSS, Inc. Japan<br>
English: <a href="http://www.sraoss.co.jp/index_en.php" rel="noreferrer" target="_blank">http://www.sraoss.co.jp/index_en.php</a><br>
Japanese:<a href="http://www.sraoss.co.jp" rel="noreferrer" target="_blank">http://www.sraoss.co.jp</a><br>
<br>
> Hi,<br>
> Thanks for your replay...<br>
> I do use online recovery in case a full recovery is needed (using<br>
> pg_basebackup - via pcp_recovery_node).<br>
> but I added an ability to perform a switchover between the nodes using<br>
> stop/detach primary - failover occurs and reattach it as secondary (using<br>
> failback script).<br>
> but as the failback finished the pgpool does not attach it as secondary!!<br>
><br>
><br>
> Can you please advice?<br>
><br>
> cohavisi<br>
><br>
><br>
> On Tue, Mar 1, 2016 at 10:41 AM, Tatsuo Ishii <<a href="mailto:ishii@postgresql.org">ishii@postgresql.org</a>> wrote:<br>
><br>
>> You should use online recovery instead of pcp_attach_node.<br>
>><br>
>> Best regards,<br>
>> --<br>
>> Tatsuo Ishii<br>
>> SRA OSS, Inc. Japan<br>
>> English: <a href="http://www.sraoss.co.jp/index_en.php" rel="noreferrer" target="_blank">http://www.sraoss.co.jp/index_en.php</a><br>
>> Japanese:<a href="http://www.sraoss.co.jp" rel="noreferrer" target="_blank">http://www.sraoss.co.jp</a><br>
>><br>
>> > Hi,<br>
>> > I have a Hugh problem regarding attaching a node (as secondary) to the<br>
>> pool<br>
>> > after I performing pcp_attach_node.<br>
>> ><br>
>> > after failover is being completed successfully and valid primary node is<br>
>> > active, i'm performing an *pcp_attach (via sql)* to the faulty node in<br>
>> > order to failback as secondary!<br>
>> ><br>
>> > *select pcp_attach_node (0,'10.10.61.99',1200,9898,'*****','*****') *<br>
>> ><br>
>> > during this command, a failback script is being executed and performs the<br>
>> > following:<br>
>> > 1. rsync between the DB nodes.<br>
>> > 2. create recovery.conf.<br>
>> > 3. startup the node(as secondary).<br>
>> ><br>
>> > *the failback could take for 20 min to finish.*<br>
>> ><br>
>> > after the failback finished *successfully* (exit status 0) and the node<br>
>> > started as *secondary* (according to postgres) - streaming replication.<br>
>> ><br>
>> > *the pgpool reportes the node status from 1 to 3 (instead of 2).*<br>
>> ><br>
>> > *** when failback finished early (less then few min) the pgpool reports<br>
>> the<br>
>> > node status as 2 - as aspected.*<br>
>> ><br>
>> ><br>
>> > please advice regarding this issue...<br>
>> ><br>
>> ><br>
>> > *Thanks,*<br>
>> > *cohavisi*<br>
>><br>
</div></div></blockquote></div><br></div>