[pgpool-hackers: 153] Re: persisting pgpool status

Huang Bambo bambo.huang at gmail.com
Fri Nov 9 00:10:46 JST 2012


Hi, Klaus,
  I think this is not the problem of pgpool2, but the way you setup your HA
system.
  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.
  You can find something help at here: http://linux-ha.org/wiki/Split_Brain
  Hope helps.

  Bambo Huang

On Thu, Nov 8, 2012 at 4:57 PM, Meister, Klaus <Meister at mecom.de> wrote:

>  Hi pgpool-hackers,****
>
> ** **
>
> we are using pgpool2-3.1.3 in a productive environment with streaming
> replication.****
>
> For the single point of failure pgpool we have a corosync/pacemaker
> configuration on each database machine.****
>
> ** **
>
> Once  we had an automatic  failover (because of a network failure) wich
> worked fine but which we did not realize!(?)****
>
> 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.****
>
> ** **
>
> To prevent this we are planning to use the pgpool_status file on a shared
> storage and use it on startup/failover/switchover …****
>
> This file seems to be written only in case of cleanly stopping the ppool.*
> ***
>
> I think it would be useful to do this every time the status of a node is
> being changed.****
>
> ** **
>
> Maybe is there another recommended way to solve our problem.****
>
> ** **
>
> With kind regards****
>
> Klaus Meister****
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> -- ****
>
> Dipl.-Phys. Klaus Meister****
>
> ** **
>
> Datenbankadministrator****
>
> mecom Medien-Communikations-Gesellschaft mbH****
>
> Mittelweg 143****
>
> D 20148 Hamburg****
>
> ** **
>
> Tel:   +49 40 4113-32824****
>
> Fax:  +49 40 451962****
>
> Web: <http://www.mecom.de/>****
>
> Registergericht Hamburg, HRB 43177****
>
> Geschäftsführer: Ulrich Wiehsalla, Barbara Bliefert****
>
> --------------------------------------------------------------****
>
> Sollten Sie nicht der beabsichtigte Empfänger sein, ****
>
> informieren Sie bitte den Absender dieser E-Mail entsprechend.****
>
> ** **
>
> _______________________________________________
> pgpool-hackers mailing list
> pgpool-hackers at pgpool.net
> http://www.pgpool.net/mailman/listinfo/pgpool-hackers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-hackers/attachments/20121108/cb25cc34/attachment.html>


More information about the pgpool-hackers mailing list