Thanks for your replay...<div>I'll check it..</div><div><br></div><div>Thanks,</div><div>ShayCÂ <span></span><br><br>On Wednesday, March 30, 2016, Tatsuo Ishii <<a href="mailto:ishii@postgresql.org">ishii@postgresql.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">> *(pgpool 3.4.2 and postgresql 9.3.5)*<br>
><br>
> During stress tests on my setup, PGpool has failed to find_primary node<br>
> after a failover!<br>
> the primary node has started but pgpool keep searched for it.<br>
> (pgpool has be restarted in order find the primary)<br>
><br>
> can you please review the log (2016-03-22 03:03:XX) and advise why the<br>
> primary node has been been detected??<br>
><br>
> scenario:<br>
><br>
> 1. killing the primary node.<br>
> 2. pgpool performed a failover.<br>
> 3. pgpool performs "follow master command".<br>
<br>
find_primary_node() first connects to the primary node (host0)'s<br>
postgres database as user = sr_check_user and password =<br>
sr_check_password. Can you make sure that psql can connect to the<br>
host0's postgres database with the user and password?<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" target="_blank">http://www.sraoss.co.jp/index_en.php</a><br>
Japanese:<a href="http://www.sraoss.co.jp" target="_blank">http://www.sraoss.co.jp</a><br>
</blockquote></div>