[pgpool-committers: 3811] pgpool: Pgpool-II should not perform ping test after bringing down the
m.usama at gmail.com
Fri Feb 24 01:24:01 JST 2017
Pgpool-II should not perform ping test after bringing down the VIP
At the time de-escalation from the master watchdog node, we should not perform
the ping test to verify if the VIP was successfully brought down or not.
The reason is, if the new master watchdog node acquires the VIP while the
resigning node is still performing the de-escalation steps, then the resigning
Pgpool-II node will falsely assume that it has failed to bring down the
delegate IP, Since it will get the positive ping result from the new master node
who has already acquired the same VIP.
Secondly, not having the delegate-IP in the configuration should not be
considered as an error case by wd_IP_up() and wd_IP_down() functions.
Since there are many possible valid scenarios where a user would not want to
have a delegate-IP. So now both wd_IP_* functions return WD_OK instead of WD_ND
when delegate_IP configuration is empty.
This issue was reported by the reporter of
bug:[pgpool-II 0000249]: watchdog sometimes fails de-escalation
The commit also contains some log message fixes.
src/watchdog/wd_escalation.c | 2 +-
src/watchdog/wd_if.c | 58 +++++++++++++++++++++-----------------------
2 files changed, 28 insertions(+), 32 deletions(-)
More information about the pgpool-committers