1PACEMAKER-CONTROLD(7) Pacemaker Configuration PACEMAKER-CONTROLD(7)
2
3
4
6 pacemaker-controld - controller properties
7
9 [dc-version=string] [cluster-infrastructure=string]
10 [cluster-name=string] [dc-deadtime=time]
11 [cluster-recheck-interval=time] [load-threshold=percentage]
12 [node-action-limit=integer] [fence-reaction=string]
13 [election-timeout=time] [shutdown-escalation=time]
14 [join-integration-timeout=time] [join-finalization-timeout=time]
15 [transition-delay=time] [stonith-watchdog-timeout=time]
16 [stonith-max-attempts=integer]
17
19 Cluster properties used by Pacemaker's controller, formerly known as
20 crmd
21
23 dc-version = string [none]
24 Version of Pacemaker on the cluster's DC.
25
26 Includes the hash which identifies the exact changeset it was built
27 from. Used for diagnostic purposes.
28
29 cluster-infrastructure = string [corosync]
30 The messaging stack on which Pacemaker is currently running.
31
32 Used for informational and diagnostic purposes.
33
34 cluster-name = string [(null)]
35 An arbitrary name for the cluster
36
37 This optional value is mostly for users' convenience as desired in
38 administration, but may also be used in Pacemaker configuration
39 rules via the #cluster-name node attribute, and by higher-level
40 tools and resource agents.
41
42 dc-deadtime = time [20s]
43 How long to wait for a response from other nodes during startup.
44
45 The "correct" value will depend on the speed/load of your network
46 and the type of switches used.
47
48 cluster-recheck-interval = time [15min]
49 Polling interval for time based changes to options, resource
50 parameters and constraints.
51
52 The Cluster is primarily event driven, however the configuration
53 can have elements that change based on time. To ensure these
54 changes take effect, we can optionally poll the cluster's status
55 for changes. Allowed values: Zero disables polling. Positive values
56 are an interval in seconds (unless other SI units are specified.
57 eg. 5min)
58
59 load-threshold = percentage [80%]
60 The maximum amount of system resources that should be used by nodes
61 in the cluster
62
63 The cluster will slow down its recovery process when the amount of
64 system resources used (currently CPU) approaches this limit
65
66 node-action-limit = integer [0]
67 The maximum number of jobs that can be scheduled per node. Defaults
68 to 2x cores
69
70 fence-reaction = string [stop]
71 How a cluster node should react if notified of its own fencing
72
73 A cluster node may receive notification of its own fencing if
74 fencing is misconfigured, or if fabric fencing is in use that
75 doesn't cut cluster communication. Allowed values are "stop" to
76 attempt to immediately stop pacemaker and stay stopped, or "panic"
77 to attempt to immediately reboot the local node, falling back to
78 stop on failure.
79
80 election-timeout = time [2min]
81 *** Advanced Use Only ***.
82
83 If need to adjust this value, it probably indicates the presence of
84 a bug.
85
86 shutdown-escalation = time [20min]
87 *** Advanced Use Only ***.
88
89 If need to adjust this value, it probably indicates the presence of
90 a bug.
91
92 join-integration-timeout = time [3min]
93 *** Advanced Use Only ***
94
95 If need to adjust this value, it probably indicates the presence of
96 a bug
97
98 join-finalization-timeout = time [30min]
99 *** Advanced Use Only ***
100
101 If you need to adjust this value, it probably indicates the
102 presence of a bug
103
104 transition-delay = time [0s]
105 *** Advanced Use Only *** Enabling this option will slow down
106 cluster recovery under all conditions
107
108 Delay cluster recovery for the configured interval to allow for
109 additional/related events to occur. Useful if your configuration is
110 sensitive to the order in which ping updates arrive.
111
112 stonith-watchdog-timeout = time [(null)]
113 How long to wait before we can assume nodes are safely down
114
115 stonith-max-attempts = integer [10]
116 How many times stonith can fail before it will no longer be
117 attempted on a target
118
120 Andrew Beekhof <andrew@beekhof.net>
121 Author.
122
123
124
125Pacemaker Configuration 11/26/2019 PACEMAKER-CONTROLD(7)