pgpool2.git / summary / log / commit / refs

commit    e13b2d2e91a13d4345eee2370243587f414494db
Author:   Muhammad Usama <m.usama@gmail.com>
Date:     Tue May 28 09:30:21 2019 +0000

    Documentation updates to reflect the changed behaviour of quarantined nodes.
    
    Mentioning about the resignation of watchdog-master when primary backend gets in
    quarantine on it, and the continuous health checking of quarantined nodes.


 doc/src/sgml/watchdog.sgml | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/doc/src/sgml/watchdog.sgml b/doc/src/sgml/watchdog.sgml
index ce838d405..815b4ddeb 100644
--- a/doc/src/sgml/watchdog.sgml
+++ b/doc/src/sgml/watchdog.sgml
@@ -410,6 +410,22 @@
         and until the master node is quarantined the <productname>Pgpool-II</productname> will not have
         any useable master backend node.
         </para>
+        <para>
+        Moreover, unlike for the failed nodes, Pgpool-II keeps the health-check running on the quarantined nodes
+        and as soon as the quarantined node becomes reachable again it gets automatically re-attached.
+        </para>
+        <para>
+        From <productname>Pgpool-II </productname><emphasis>V4.1</emphasis> onwards. If the watchdog-master node
+        fails to build the consensus for primary backend node failover and the primary backend node gets into a
+        quarantine state, then it resigns from its master/coordinator responsibilities and lowers its wd_priority
+        for next leader election and let the cluster elect some different new leader.
+            <note>
+            <para>
+            When the master node fails to build the consensus for standby backend node failure, it takes no action
+            and similarly quarantined standby backend nodes on watchdog-master do not trigger a new leader election.
+            </para>
+            </note>
+        </para>
         <para>
           Default is on.
         </para>


[parent: 33df0d33df1c]