File jsc#ECO-1611-0009-Doc-Pacemaker-Explained-document-priority-fencing-de-1.1.patch of Package pacemaker.19778
From d7bab0edf02306b227e7d6b5bbac43f8b0a7883c Mon Sep 17 00:00:00 2001 From: "Gao,Yan" <ygao@suse.com> Date: Wed, 18 Mar 2020 16:30:35 +0100 Subject: [PATCH 09/15] Doc: Pacemaker Explained: document priority-fencing-delay cluster option --- doc/Pacemaker_Explained/en-US/Ch-Options.txt | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/doc/Pacemaker_Explained/en-US/Ch-Options.txt b/doc/Pacemaker_Explained/en-US/Ch-Options.txt index 7981cd110..db532bf09 100644 --- a/doc/Pacemaker_Explained/en-US/Ch-Options.txt +++ b/doc/Pacemaker_Explained/en-US/Ch-Options.txt @@ -241,6 +241,22 @@ indexterm:[Cluster,Option,concurrent-fencing] Is the cluster allowed to initiate multiple fence actions concurrently? '(since 1.1.15)' +| 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] -- 2.26.1
