Hi, Klaus,<br> I think this is not the problem of pgpool2, but the way you setup your HA system.<br> Obviously you problem is of split-brain. And I think most HA service can resolve this problem, such as using fence device can reboot node and keep another one as active, and that rebooted node can do recover and run as hot-backup node.<br>
You can find something help at here: <a href="http://linux-ha.org/wiki/Split_Brain">http://linux-ha.org/wiki/Split_Brain</a><br><div class="gmail_extra"> Hope helps.<br><br> Bambo Huang<br><br><div class="gmail_quote">
On Thu, Nov 8, 2012 at 4:57 PM, Meister, Klaus <span dir="ltr"><<a href="mailto:Meister@mecom.de" target="_blank">Meister@mecom.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div link="blue" vlink="purple" lang="DE">
<div>
<p class="">Hi pgpool-hackers,<u></u><u></u></p>
<p class=""><u></u> <u></u></p>
<p class="">we are using pgpool2-3.1.3 in a productive environment with streaming replication.<u></u><u></u></p>
<p class="">For the single point of failure pgpool we have a corosync/pacemaker configuration on each database machine.<u></u><u></u></p>
<p class=""><u></u> <u></u></p>
<p class="">Once we had an automatic failover (because of a network failure) wich worked fine but which we did not realize!(?)<u></u><u></u></p>
<p class="">2 weeks later there was another failover (wich worked fine too :) and we were back on the obsolete database which was still up and open.<u></u><u></u></p>
<p class=""><u></u> <u></u></p>
<p class="">To prevent this we are planning to use the pgpool_status file on a shared storage and use it on startup/failover/switchover …<u></u><u></u></p>
<p class="">This file seems to be written only in case of cleanly stopping the ppool.<u></u><u></u></p>
<p class="">I think it would be useful to do this every time the status of a node is being changed.<u></u><u></u></p>
<p class=""><u></u> <u></u></p>
<p class="">Maybe is there another recommended way to solve our problem.<u></u><u></u></p>
<p class=""><u></u> <u></u></p>
<p class="">With kind regards<u></u><u></u></p>
<p class="">Klaus Meister<u></u><u></u></p>
<p class=""><u></u> <u></u></p>
<p class=""><u></u> <u></u></p>
<p class=""><u></u> <u></u></p>
<p class=""><u></u> <u></u></p>
<p class="">-- <u></u><u></u></p>
<p class="">Dipl.-Phys. Klaus Meister<u></u><u></u></p>
<p class=""><u></u> <u></u></p>
<p class="">Datenbankadministrator<u></u><u></u></p>
<p class="">mecom Medien-Communikations-Gesellschaft mbH<u></u><u></u></p>
<p class="">Mittelweg 143<u></u><u></u></p>
<p class="">D 20148 Hamburg<u></u><u></u></p>
<p class=""><u></u> <u></u></p>
<p class="">Tel: <a href="tel:%2B49%2040%204113-32824" value="+4940411332824" target="_blank">+49 40 4113-32824</a><u></u><u></u></p>
<p class="">Fax: <a href="tel:%2B49%2040%20451962" value="+4940451962" target="_blank">+49 40 451962</a><u></u><u></u></p>
<p class="">Web: <<a href="http://www.mecom.de/" target="_blank">http://www.mecom.de/</a>><u></u><u></u></p>
<p class="">Registergericht Hamburg, HRB 43177<u></u><u></u></p>
<p class="">Geschäftsführer: Ulrich Wiehsalla, Barbara Bliefert<u></u><u></u></p>
<p class="">--------------------------------------------------------------<u></u><u></u></p>
<p class="">Sollten Sie nicht der beabsichtigte Empfänger sein, <u></u><u></u></p>
<p class="">informieren Sie bitte den Absender dieser E-Mail entsprechend.<u></u><u></u></p>
<p class=""><u></u> <u></u></p>
</div>
</div>
<br>_______________________________________________<br>
pgpool-hackers mailing list<br>
<a href="mailto:pgpool-hackers@pgpool.net">pgpool-hackers@pgpool.net</a><br>
<a href="http://www.pgpool.net/mailman/listinfo/pgpool-hackers" target="_blank">http://www.pgpool.net/mailman/listinfo/pgpool-hackers</a><br>
<br></blockquote></div><br></div>