[pgpool-hackers: 1742] Re: [pgpool-II 0000228]: pgpool doesnt de-escalate IP in case netowkr restored

[Tatsuo Ishii]

Usama,

Can you please take care of this.
This is a watchdog issue.

Peng,

Please add this to the Pgpool-II development wiki.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp

From: pgpool Bug Tracker <bugtracker at pgpool.net>
Subject: [pgpool-II 0000228]: pgpool doesnt de-escalate IP in case netowkr restored
Date: Tue, 2 Aug 2016 01:53:03 +0900
Message-ID: <62005dfc7b76603f5e1cd6160cb3c2b5 at www.pgpool.net>

> 
> The following issue has been SUBMITTED. 
> ====================================================================== 
> http://www.pgpool.net/mantisbt/view.php?id=228 
> ====================================================================== 
> Reported By:                supp_k
> Assigned To:                
> ====================================================================== 
> Project:                    pgpool-II
> Issue ID:                   228
> Category:                   Bug
> Reproducibility:            always
> Severity:                   major
> Priority:                   high
> Status:                     new
> ====================================================================== 
> Date Submitted:             2016-08-02 01:53 JST
> Last Modified:              2016-08-02 01:53 JST
> ====================================================================== 
> Summary:                    pgpool doesnt de-escalate IP in case netowkr
> restored
> Description: 
> Pgpool doesn't de-escalate IP address in case the split brain is resolved when
> it turns from Master into Standby.
> 
> Steps to Reproduce: 
> Environment:
> 1) Pgpool A (Master) hosts VIP (virtual IP)
> 2) Pgpool B (Standby)
> Watchdog and heartbit processes are OK.
> 
> Steps to reproduce:
> - emulate network failure between Pgpool A & Pgpool B for the heartbit receive
> time period. When the heartbit time is exceeded Pgpool initiates voting and up
> the VIP - it is Ok! Now we have 2 Pgpool masters within the network => it is the
> "split brain" case.
> 
> - restore network connectivity between Pgpool A & Pgpool B => pgpools restart
> voting and one of the masters turns into Standby (let it be the Pgpool B) - it
> is OK as well but at the same moment the Pgpool B doesnt down (ip addr del ...)
> the VIP. Should it be?
> 
> ====================================================================== 
> 
> Issue History 
> Date Modified    Username       Field                    Change               
> ====================================================================== 
> 2016-08-02 01:53 supp_k         New Issue                                    
> ======================================================================
>