|
 |
ed4e54 |
From 5656b7d486569702ea6f3fe695c2fba366c970ac Mon Sep 17 00:00:00 2001
|
|
|
ed4e54 |
From: Ken Gaillot <kgaillot@redhat.com>
|
|
|
ed4e54 |
Date: Thu, 12 Dec 2019 09:26:00 -0600
|
|
|
ed4e54 |
Subject: [PATCH 18/18] Doc: Pacemaker Explained: document shutdown lock
|
|
|
ed4e54 |
options
|
|
|
ed4e54 |
|
|
|
ed4e54 |
---
|
|
|
ed4e54 |
doc/Pacemaker_Explained/en-US/Ch-Options.txt | 27 +++++++++++++++++++++++++++
|
|
|
ed4e54 |
1 file changed, 27 insertions(+)
|
|
|
ed4e54 |
|
|
|
ed4e54 |
diff --git a/doc/Pacemaker_Explained/en-US/Ch-Options.txt b/doc/Pacemaker_Explained/en-US/Ch-Options.txt
|
|
|
ed4e54 |
index f864987..35856aa 100644
|
|
|
ed4e54 |
--- a/doc/Pacemaker_Explained/en-US/Ch-Options.txt
|
|
|
ed4e54 |
+++ b/doc/Pacemaker_Explained/en-US/Ch-Options.txt
|
|
|
ed4e54 |
@@ -389,6 +389,33 @@ rules with +date_spec+ are only guaranteed to be checked this often, and it
|
|
|
ed4e54 |
also serves as a fail-safe for certain classes of scheduler bugs. A value of 0
|
|
|
ed4e54 |
disables this polling; positive values are a time interval.
|
|
|
ed4e54 |
|
|
|
ed4e54 |
+| shutdown-lock | false |
|
|
|
ed4e54 |
+The default of false allows active resources to be recovered elsewhere when
|
|
|
ed4e54 |
+their node is cleanly shut down, which is what the vast majority of users will
|
|
|
ed4e54 |
+want. However, some users prefer to make resources highly available only for
|
|
|
ed4e54 |
+failures, with no recovery for clean shutdowns. If this option is true,
|
|
|
ed4e54 |
+resources active on a node when it is cleanly shut down are kept "locked" to
|
|
|
ed4e54 |
+that node (not allowed to run elsewhere) until they start again on that node
|
|
|
ed4e54 |
+after it rejoins (or for at most shutdown-lock-limit, if set). Stonith
|
|
|
ed4e54 |
+resources and Pacemaker Remote connections are never locked. Clone and bundle
|
|
|
ed4e54 |
+instances and the master role of promotable clones are currently never locked,
|
|
|
ed4e54 |
+though support could be added in a future release. Locks may be manually
|
|
|
ed4e54 |
+cleared using the `--refresh` option of `crm_resource` (both the resource and
|
|
|
ed4e54 |
+node must be specified; this works with remote nodes if their connection
|
|
|
ed4e54 |
+resource's target-role is set to Stopped, but not if Pacemaker Remote is
|
|
|
ed4e54 |
+stopped on the remote node without disabling the connection resource).
|
|
|
ed4e54 |
+indexterm:[shutdown-lock,Cluster Option]
|
|
|
ed4e54 |
+indexterm:[Cluster,Option,shutdown-lock]
|
|
|
ed4e54 |
+
|
|
|
ed4e54 |
+| shutdown-lock-limit | 0 |
|
|
|
ed4e54 |
+If shutdown-lock is true, and this is set to a nonzero time duration, locked
|
|
|
ed4e54 |
+resources will be allowed to start after this much time has passed since the
|
|
|
ed4e54 |
+node shutdown was initiated, even if the node has not rejoined. (This works
|
|
|
ed4e54 |
+with remote nodes only if their connection resource's target-role is set to
|
|
|
ed4e54 |
+Stopped.)
|
|
|
ed4e54 |
+indexterm:[shutdown-lock-limit,Cluster Option]
|
|
|
ed4e54 |
+indexterm:[Cluster,Option,shutdown-lock-limit]
|
|
|
ed4e54 |
+
|
|
|
ed4e54 |
| remove-after-stop | FALSE |
|
|
|
ed4e54 |
indexterm:[remove-after-stop,Cluster Option]
|
|
|
ed4e54 |
indexterm:[Cluster,Option,remove-after-stop]
|
|
|
ed4e54 |
--
|
|
|
ed4e54 |
1.8.3.1
|
|
|
ed4e54 |
|