[pgpool-general: 4560] find_primary_node failed ...
Shay Cohavi
cohavisi at gmail.com
Tue Mar 22 19:16:18 JST 2016
Hi,
*(pgpool 3.4.2 and postgresql 9.3.5)*
During stress tests on my setup, PGpool has failed to find_primary node
after a failover!
the primary node has started but pgpool keep searched for it.
(pgpool has be restarted in order find the primary)
can you please review the log (2016-03-22 03:03:XX) and advise why the
primary node has been been detected??
scenario:
1. killing the primary node.
2. pgpool performed a failover.
3. pgpool performs "follow master command".
Thanks,
cohavisi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pgpool.net/pipermail/pgpool-general/attachments/20160322/c4c0186e/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: failure_pgpool.rtf
Type: application/rtf
Size: 476019 bytes
Desc: not available
URL: <http://www.pgpool.net/pipermail/pgpool-general/attachments/20160322/c4c0186e/attachment.rtf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: primary_postgres_log.rtf
Type: application/rtf
Size: 17900 bytes
Desc: not available
URL: <http://www.pgpool.net/pipermail/pgpool-general/attachments/20160322/c4c0186e/attachment-0001.rtf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pgpool.conf
Type: application/octet-stream
Size: 21166 bytes
Desc: not available
URL: <http://www.pgpool.net/pipermail/pgpool-general/attachments/20160322/c4c0186e/attachment.obj>
More information about the pgpool-general
mailing list