From 29acd10f37481d5f7feb79ec9b569b66705091db Mon Sep 17 00:00:00 2001 From: Ian Barwick Date: Fri, 22 Mar 2019 15:42:12 +0900 Subject: [PATCH] doc: update release notes --- HISTORY | 2 ++ doc/appendix-release-notes.sgml | 20 ++++++++++++++------ 2 files changed, 16 insertions(+), 6 deletions(-) diff --git a/HISTORY b/HISTORY index 1424b60a..a216af30 100644 --- a/HISTORY +++ b/HISTORY @@ -22,6 +22,8 @@ candidates (Ian) repmgrd: add option "connection_check_type" (Ian) repmgrd: improve witness monitoring when primary node not available (Ian) + repmgrd: handle situation where a primary has unexpectedly appeared + during failover; GitHub #420 (Ian) 4.2 2018-10-24 repmgr: add parameter "shutdown_check_timeout" for use by "standby switchover"; diff --git a/doc/appendix-release-notes.sgml b/doc/appendix-release-notes.sgml index cfa30ca6..bc4e2287 100644 --- a/doc/appendix-release-notes.sgml +++ b/doc/appendix-release-notes.sgml @@ -152,13 +152,13 @@ REPMGRD_OPTS="--daemonize=false" repmgrd will no longer consider nodes where repmgrd - is not running as promotion candidates. + is not running as promotion candidates. + + + Previously, if repmgrd was not running on a node, but + that node qualified as the promotion candidate, it would never be promoted due to + the absence of a running repmgrd. - - Previously, if repmgrd was not running on a node, but - that node qualified as the promotion candidate, it would never be promoted due to - the absence of a running repmgrd. - @@ -188,6 +188,14 @@ REPMGRD_OPTS="--daemonize=false" + + + In a failover situation, repmgrd will not attempt to promote a + node if another standby has already appeared (e.g. by being promoted manually). + GitHub #420. + + +