From 42515908331e7392704345c360da9e9bce439ad8 Mon Sep 17 00:00:00 2001 From: Ian Barwick Date: Thu, 14 Mar 2019 15:42:19 +0900 Subject: [PATCH] doc: update "connection_check_type" descriptions --- doc/appendix-release-notes.sgml | 63 +++++++++++++++++---------------- doc/repmgrd-configuration.sgml | 15 +++++--- 2 files changed, 43 insertions(+), 35 deletions(-) diff --git a/doc/appendix-release-notes.sgml b/doc/appendix-release-notes.sgml index 6aafea77..cfa30ca6 100644 --- a/doc/appendix-release-notes.sgml +++ b/doc/appendix-release-notes.sgml @@ -24,15 +24,15 @@ - On Debian-based systems, including Ubuntu, if using repmgrd - please ensure that in the file /etc/init.d/repmgrd, the parameter - REPMGRD_OPTS contains "--daemonize=false", e.g.: - + On Debian-based systems, including Ubuntu, if using repmgrd + please ensure that in the file /etc/init.d/repmgrd, the parameter + REPMGRD_OPTS contains "--daemonize=false", e.g.: + # additional options REPMGRD_OPTS="--daemonize=false" - For further details, see repmgrd configuration on Debian/Ubuntu. + For further details, see repmgrd configuration on Debian/Ubuntu. @@ -99,11 +99,11 @@ REPMGRD_OPTS="--daemonize=false" repmgr cluster show: - differentiate between unreachable nodes and nodes which are running but rejecting connections. + differentiate between unreachable nodes and nodes which are running but rejecting connections. - This makes it possible to see whether a node is unreachable at network level, - or if it is running but rejecting connections for some reason. + This makes it possible to see whether a node is unreachable at network level, + or if it is running but rejecting connections for some reason. @@ -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. + @@ -168,7 +168,8 @@ REPMGRD_OPTS="--daemonize=false" Possible values are ping (default; uses PQping() to - determine server availability); and connection (determines server availability + determine server availability), connection (attempst to make a new connection to + the upstream node), and query (determines server availability by executing an SQL statement on the node via the existing connection). @@ -223,7 +224,7 @@ REPMGRD_OPTS="--daemonize=false" &repmgr;: when executing repmgr standby switchover, avoid a potential race condition when comparing received WAL on the standby to the primary's shutdown location, - as the standby's walreceiver may not have yet flushed all received WAL to disk. GitHub #518. + as the standby's walreceiver may not have yet flushed all received WAL to disk. GitHub #518. @@ -231,7 +232,7 @@ REPMGRD_OPTS="--daemonize=false" &repmgr;: when executing repmgr standby switchover, - verify the standby (promotion candidate) is currently attached to the primary (demotion candidate). GitHub #519. + verify the standby (promotion candidate) is currently attached to the primary (demotion candidate). GitHub #519. @@ -245,25 +246,25 @@ REPMGRD_OPTS="--daemonize=false" repmgr cluster show: - fix display of node IDs with multiple digits. + fix display of node IDs with multiple digits. - + ensure repmgr primary unregister - behaves correctly when executed on a witness server. GitHub #548. + behaves correctly when executed on a witness server. GitHub #548. - + repmgr node check - will only consider physical replication slots, as the purpose - of slot checks is to warn about potential issues with - streaming replication standbys which are no longer attached. - - + will only consider physical replication slots, as the purpose + of slot checks is to warn about potential issues with + streaming replication standbys which are no longer attached. + + @@ -289,15 +290,15 @@ REPMGRD_OPTS="--daemonize=false" - On Debian-based systems, including Ubuntu, if using repmgrd - please ensure that the in the file /etc/init.d/repmgrd, the parameter - REPMGRD_OPTS contains "--daemonize=false", e.g.: - + On Debian-based systems, including Ubuntu, if using repmgrd + please ensure that the in the file /etc/init.d/repmgrd, the parameter + REPMGRD_OPTS contains "--daemonize=false", e.g.: + # additional options REPMGRD_OPTS="--daemonize=false" - For further details, see repmgrd daemon configuration on Debian/Ubuntu. + For further details, see repmgrd daemon configuration on Debian/Ubuntu. diff --git a/doc/repmgrd-configuration.sgml b/doc/repmgrd-configuration.sgml index bb70301d..a429bcae 100644 --- a/doc/repmgrd-configuration.sgml +++ b/doc/repmgrd-configuration.sgml @@ -76,9 +76,16 @@ connection - determines server availability + by attempt ingto make a new connection to the upstream node + + + + + query - determines server availability by executing an SQL statement on the node via the existing connection + @@ -92,7 +99,7 @@ The number of attempts (default: 6) will be made to reconnect to an unreachable - upstream node before initiating a failover. + upstream node before initiating a failover. There will be an interval of seconds between each reconnection @@ -124,7 +131,7 @@ - + Interval (in seconds) after which repmgrd will terminate if either of the servers (local node and or upstream node) being monitored is no longer available (degraded monitoring mode). @@ -132,8 +139,8 @@ -1 (default) disables this timeout completely. - - + +