[pgpool-general: 5226] Re: Questionable Failover

Yates, James C. -ND James.C.Yates.-ND at disney.com
Thu Jan 12 02:06:56 JST 2017


I was not expecting that behavior from PgPool.  I was under the impression that a failover would not occur unless the primary/master server had issues.

On Jan 11, 2017, at 3:32 AM, Muhammad Usama <m.usama at gmail.com<mailto:m.usama at gmail.com>> wrote:

Hi

It seems like there was a temporary network glitch/failure between the two data centers around "Jan 05 00:04:29" time triggered the failover of backend node0.

If we look at the logs of each node around this time we can see that the Pgpool-II nodes in the first data center (dbserver1 and dbserver2) were not able to connect to PostgreSQL on dbserver3 that is located in the second data center, and at the very same time the Pgpool-II on dbserver3 was also having the connection problem with PostgreSQL located on the first data center on dbserver1. All this points towards the connectivity issue between the two data centers.

Also, apparently the network issue seems to have resolved after a couple of minutes, but till that time the PostgreSQL node failure was already registered by Pgpool-II on dbserver3 and the failover was triggered.

Thanks
Best regards
Muhammad Usama

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20170111/8c4fee84/attachment.html>


More information about the pgpool-general mailing list