Skip to content

Commit cf22ac4

Browse files
committed
Doc: Pacemaker Explained: document priority-fencing-delay cluster option
1 parent 17726a8 commit cf22ac4

1 file changed

Lines changed: 14 additions & 0 deletions

File tree

doc/Pacemaker_Explained/en-US/Ch-Options.txt

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -292,6 +292,20 @@ are +stop+ to attempt to immediately stop pacemaker and stay stopped, or
292292
on failure. The default is likely to be changed to +panic+ in a future release.
293293
'(since 2.0.3)'
294294

295+
| priority-fencing-delay | |
296+
indexterm:[priority-fencing-delay,Cluster Option]
297+
indexterm:[Cluster,Option,priority-fencing-delay]
298+
Enforce specified delay for the fencings that are targeting the lost
299+
nodes with the highest total resource priority in case we don't
300+
have the majority of the nodes in our cluster partition, so that
301+
the more significant nodes potentially win any fencing match,
302+
which is especially meaningful under split-brain of 2-node
303+
cluster. If all the nodes have equal priority, then any
304+
pcmk_delay_base/max configured for the corresponding fencing
305+
resources will be applied. Otherwise as long as it's set, even if
306+
to 0, it takes precedence over any configured pcmk_delay_base/max.
307+
By default, priority fencing delay is disabled.
308+
295309
| cluster-delay | 60s |
296310
indexterm:[cluster-delay,Cluster Option]
297311
indexterm:[Cluster,Option,cluster-delay]

0 commit comments

Comments
 (0)