File jsc#ECO-1611-0009-Doc-Pacemaker-Explained-document-priority-fencing-de.patch of Package pacemaker.21299
From b0b17105ac2987e04f4085b4b7be601854347386 Mon Sep 17 00:00:00 2001 From: "Gao,Yan" <ygao@suse.com> Date: Wed, 18 Mar 2020 16:30:35 +0100 Subject: [PATCH 9/9] Doc: Pacemaker Explained: document priority-fencing-delay cluster option --- doc/Pacemaker_Explained/en-US/Ch-Options.txt | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) Index: pacemaker-2.0.1+20190417.13d370ca9/doc/Pacemaker_Explained/en-US/Ch-Options.txt =================================================================== --- pacemaker-2.0.1+20190417.13d370ca9.orig/doc/Pacemaker_Explained/en-US/Ch-Options.txt +++ pacemaker-2.0.1+20190417.13d370ca9/doc/Pacemaker_Explained/en-US/Ch-Options.txt @@ -281,6 +281,22 @@ indexterm:[concurrent-fencing,Cluster Op indexterm:[Cluster,Option,concurrent-fencing] Is the cluster allowed to initiate multiple fence actions concurrently? +| priority-fencing-delay | | +indexterm:[priority-fencing-delay,Cluster Option] +indexterm:[Cluster,Option,priority-fencing-delay] +Enforce specified delay for the fencings that are targeting the lost +nodes with the highest total resource priority in case we don't +have the majority of the nodes in our cluster partition, so that +the more significant nodes potentially win any fencing match, +which is especially meaningful under split-brain of 2-node +cluster. A promoted resource instance takes the base priority + 1 +on calculation if the base priority is not 0. If all the nodes +have equal priority, then any pcmk_delay_base/max configured for +the corresponding fencing resources will be applied. Otherwise as +long as it's set, even if to 0, it takes precedence over any +configured pcmk_delay_base/max. By default, priority fencing +delay is disabled. + | cluster-delay | 60s | indexterm:[cluster-delay,Cluster Option] indexterm:[Cluster,Option,cluster-delay]
