[pgpool-general: 2416] Re: watchdog: different statuses on different pgpool nodes.
Lazaro Ruben Garcia Martinez
lgarciam at vnz.uci.cu
Wed Jan 15 22:28:48 JST 2014
Try to start pgpool with -D option. The purpose of this option is discard pgpool_status file and do not restore previous status. May be possible that some time ago the server 1 was stopped and this result was stored in pgpool_status file.
Regards.
________________________________________
De: pgpool-general-bounces at pgpool.net [pgpool-general-bounces at pgpool.net] En nombre de Yugo Nagata [nagata at sraoss.co.jp]
Enviado el: miércoles, 15 de enero de 2014 5:26
Para: Sergey Arlashin
CC: pgpool-general at pgpool.net
Asunto: [pgpool-general: 2413] Re: watchdog: different statuses on different pgpool nodes.
Hi,
On Wed, 15 Jan 2014 12:44:40 +0400
Sergey Arlashin <sergeyarl.maillist at gmail.com> wrote:
> Hi!
>
> I'm trying set up watchdog and cannot figure out why sometimes I get different statuses on different pgpool nodes. It looks like this:
>
> Two nodes : pgpool-node1and pgpool-node2. Watchdog mutual IP address is currently assigned to pgpool-node1.
>
> pgpool-node1:~# psql -U postgres -h watchdog.mutual-ip -p 9999
>
> Password for user postgres:
> psql (9.3.2)
> Type "help" for help.
>
> postgres=# show pool_nodes;
> node_id | hostname | port | status | lb_weight | role
> ---------+---------------+------+--------+-----------+---------
> 0 | db-node1.site | 5432 | 2 | 0.500000 | primary
> 1 | db-node2.site | 5432 | 2 | 0.500000 | standby
> (2 rows)
>
>
>
> pgpool-node2:~# psql -U postgres -h localhost -p 9999
> Password for user postgres:
> psql (9.3.2)
> Type "help" for help.
>
> postgres=# show pool_nodes;
> node_id | hostname | port | status | lb_weight | role
> ---------+---------------+------+--------+-----------+---------
> 0 | db-node1.site | 5432 | 2 | 0.500000 | primary
> 1 | db-node2.site | 5432 | 3 | 0.500000 | standby
> (2 rows)
This means that pgpool on pgpool-node2 regards backend node #1 as down.
If there are no messages about failover in the log, this might be because
pgpool read old pgpool_status at startup for lack of -D option.
>
> I cannot see any problems in pgpool logs. Or any other indication that something goes wrong.
>
> Could you please tell me why this could happen?
>
>
> Thanks in advance.
>
> --
> Best regards,
> Sergey Arlashin
>
>
> _______________________________________________
> pgpool-general mailing list
> pgpool-general at pgpool.net
> http://www.pgpool.net/mailman/listinfo/pgpool-general
--
Yugo Nagata <nagata at sraoss.co.jp>
_______________________________________________
pgpool-general mailing list
pgpool-general at pgpool.net
http://www.pgpool.net/mailman/listinfo/pgpool-general
Fin a la injusticia, LIBERTAD AHORA A NUESTROS CINCO COMPATRIOTAS QUE SE ENCUENTRAN INJUSTAMENTE EN PRISIONES DE LOS EEUU!
http://www.antiterroristas.cu
http://justiciaparaloscinco.wordpress.com
Fin a la injusticia, LIBERTAD AHORA A NUESTROS CINCO COMPATRIOTAS QUE SE ENCUENTRAN INJUSTAMENTE EN PRISIONES DE LOS EEUU!
http://www.antiterroristas.cu
http://justiciaparaloscinco.wordpress.com
More information about the pgpool-general
mailing list