[pgpool-general: 2995] Last node in pgpool chain failover

[Long On]

Hello,

I have 2 postgresql nodes, 01 (primary) and 02 (standby), set up with
postgresql streaming replication. pgpool2 works well with this initial
configuration.

postgresql 01 is stopped to trigger failover to 02. This too is working
well with pgpool2, as indicated by log below. postgresql 02 becomes new
master.

2014-06-29 20:33:41 LOG:   pid 16186: wd_end_interlock: end interlocking
2014-06-29 20:33:42 LOG:   pid 16186: failover: set new primary node: -1
2014-06-29 20:33:42 LOG:   pid 16186: failover: set new master node: 1
2014-06-29 20:33:42 LOG:   pid 16186: failover done. shutdown host 01(5432)

At this point I recover postgresql 01 to become a standby to 02. Connection
via pgpool2 works well here too.

Next, postgresql 02 (primary) is stopped to trigger failover back to 01.
Failover of the two postgresql back-ends works the same way as above. 01 is
new master and 02 is standby.

However, pgpool2 is not able to recognize 01 has become new master. It
fails to set new master node: 0, as seen below. Connection via pgpool2
result in connection refused.

2014-06-29 20:59:52 LOG:   pid 16186: wd_end_interlock: end interlocking
2014-06-29 20:59:53 LOG:   pid 16186: failover: set new primary node: -1
2014-06-29 20:59:53 LOG:   pid 16186: failover done. shutdown host 02(5432)

I am new to postgresql and pgpool so I may have missed some configuration
settings. Looking around the web haven't turn up any helpful hints yet.

Any idea how I can fix this?

Your help is much appreciated.

Regards,
Long
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20140630/e5b713ab/attachment.html>