38
35
when nothing is found on disk.
41
indexterm:[epoch Cluster Option]
42
indexterm:[Cluster Options,epoch]
38
indexterm:[epoch,Cluster Option]
39
indexterm:[Cluster,Option,epoch]
43
40
Incremented every time the configuration is updated (usually by the admin)
46
indexterm:[num_updates Cluster Option]
47
indexterm:[Cluster Options,num_updates]
43
indexterm:[num_updates,Cluster Option]
44
indexterm:[Cluster,Option,num_updates]
48
45
Incremented every time the configuration or status is updated (usually by the cluster)
50
47
|=========================================================
53
50
.Properties Controlling Validation
54
[width="95%",cols="1m,5<",options="header",align="center"]
51
[width="95%",cols="2m,5<",options="header",align="center"]
55
52
|=========================================================
56
53
|Field |Description
59
indexterm:[validate-with Cluster Option]
60
indexterm:[Cluster Options,validate-with]
56
indexterm:[validate-with,Cluster Option]
57
indexterm:[Cluster,Option,validate-with]
61
58
Determines the type of validation being done on the configuration. If
62
59
set to "none", the cluster will not verify that updates conform to the
63
60
DTD (nor reject ones that don't). This option can be useful when
68
65
== Fields Maintained by the Cluster ==
70
67
.Properties Maintained by the Cluster
71
[width="95%",cols="1m,5<",options="header",align="center"]
68
[width="95%",cols="2m,5<",options="header",align="center"]
72
69
|=========================================================
73
70
|Field |Description
76
indexterm:[crm-debug-origin Cluster Fields]
77
indexterm:[Cluster Fields,crm-debug-origin]
78
Indicates where the last update came from. Informational purposes only.
80
72
|cib-last-written |
81
indexterm:[cib-last-written Cluster Fields]
82
indexterm:[Cluster Fields,cib-last-written]
73
indexterm:[cib-last-written,Cluster Property]
74
indexterm:[Cluster,Property,cib-last-written]
83
75
Indicates when the configuration was last written to disk. Informational purposes only.
86
indexterm:[dc-uuid Cluster Fields]
87
indexterm:[Cluster Fields,dc-uuid]
78
indexterm:[dc-uuid,Cluster Property]
79
indexterm:[Cluster,Property,dc-uuid]
88
80
Indicates which cluster node is the current leader. Used by the
89
81
cluster when placing resources and determining the order of some
93
indexterm:[have-quorum Cluster Fields]
94
indexterm:[Cluster Fields,have-quorum]
85
indexterm:[have-quorum,Cluster Property]
86
indexterm:[Cluster,Property,have-quorum]
95
87
Indicates if the cluster has quorum. If false, this may mean that the
96
88
cluster cannot start resources or fence other nodes. See
97
89
+no-quorum-policy+ below.
133
128
== Available Cluster Options ==
135
[width="95%",cols="5m,2m,13",options="header",align="center"]
130
[width="95%",cols="5m,2,11<",options="header",align="center"]
136
131
|=========================================================
137
132
|Option |Default |Description
139
134
| batch-limit | 30 |
140
indexterm:[batch-limit Cluster Options]
141
indexterm:[Cluster Options,batch-limit]
135
indexterm:[batch-limit,Cluster Option]
136
indexterm:[Cluster,Option,batch-limit]
142
137
The number of jobs that the TE is allowed to execute in parallel. The
143
138
"correct" value will depend on the speed and load of your network and
146
141
| migration-limit | -1 (unlimited) |
147
indexterm:[migration-limit Cluster Options]
148
indexterm:[Cluster Options,migration-limit]
142
indexterm:[migration-limit,Cluster Option]
143
indexterm:[Cluster,Option,migration-limit]
149
144
The number of migration jobs that the TE is allowed to execute in
150
145
parallel on a node.
152
147
| no-quorum-policy | stop |
153
indexterm:[no-quorum-policy Cluster Options]
154
indexterm:[Cluster Options,no-quorum-policy]
148
indexterm:[no-quorum-policy,Cluster Option]
149
indexterm:[Cluster,Option,no-quorum-policy]
155
150
What to do when the cluster does not have quorum. Allowed values:
157
152
* ignore - continue all resource management
158
154
* freeze - continue resource management, but don't recover resources from nodes not in the affected partition
159
156
* stop - stop all resources in the affected cluster partition
160
158
* suicide - fence all nodes in the affected cluster partition
162
160
| symmetric-cluster | TRUE |
163
indexterm:[symmetric-cluster Cluster Options]
164
indexterm:[Cluster Options,symmetric-cluster]
161
indexterm:[symmetric-cluster,Cluster Option]
162
indexterm:[Cluster,Option,symmetric-cluster]
165
163
Can all resources run on any node by default?
167
165
| stonith-enabled | TRUE |
168
indexterm:[stonith-enabled Cluster Options]
169
indexterm:[Cluster Options,stonith-enabled]
166
indexterm:[stonith-enabled,Cluster Option]
167
indexterm:[Cluster,Option,stonith-enabled]
170
168
Should failed nodes and nodes with resources that can't be stopped be
171
169
shot? If you value your data, set up a STONITH device and enable this.
174
172
one or more STONITH resources have been configured also.
176
174
| stonith-action | reboot |
177
indexterm:[stonith-action Cluster Options]
178
indexterm:[Cluster Options,stonith-action]
179
Action to send to STONITH device. Allowed values: reboot, poweroff.
175
indexterm:[stonith-action,Cluster Option]
176
indexterm:[Cluster,Option,stonith-action]
177
Action to send to STONITH device. Allowed values: reboot, off.
178
The value 'poweroff' is also allowed, but is only used for
181
181
| cluster-delay | 60s |
182
indexterm:[cluster-delay Cluster Options]
183
indexterm:[Cluster Options,cluster-delay]
182
indexterm:[cluster-delay,Cluster Option]
183
indexterm:[Cluster,Option,cluster-delay]
184
184
Round trip delay over the network (excluding action execution). The
185
185
"correct" value will depend on the speed and load of your network and
188
188
| stop-orphan-resources | TRUE |
189
indexterm:[stop-orphan-resources Cluster Options]
190
indexterm:[Cluster Options,stop-orphan-resources]
189
indexterm:[stop-orphan-resources,Cluster Option]
190
indexterm:[Cluster,Option,stop-orphan-resources]
191
191
Should deleted resources be stopped?
193
193
| stop-orphan-actions | TRUE |
194
indexterm:[stop-orphan-actions Cluster Options]
195
indexterm:[Cluster Options,stop-orphan-actions]
194
indexterm:[stop-orphan-actions,Cluster Option]
195
indexterm:[Cluster,Option,stop-orphan-actions]
196
196
Should deleted actions be cancelled?
198
198
| start-failure-is-fatal | TRUE |
199
indexterm:[start-failure-is-fatal Cluster Options]
200
indexterm:[Cluster Options,start-failure-is-fatal]
199
indexterm:[start-failure-is-fatal,Cluster Option]
200
indexterm:[Cluster,Option,start-failure-is-fatal]
201
201
When set to FALSE, the cluster will instead use the resource's
202
202
+failcount+ and value for +resource-failure-stickiness+.
204
204
| pe-error-series-max | -1 (all) |
205
indexterm:[pe-error-series-max Cluster Options]
206
indexterm:[Cluster Options,pe-error-series-max]
205
indexterm:[pe-error-series-max,Cluster Option]
206
indexterm:[Cluster,Option,pe-error-series-max]
207
207
The number of PE inputs resulting in ERRORs to save. Used when reporting problems.
209
209
| pe-warn-series-max | -1 (all) |
210
indexterm:[pe-warn-series-max Cluster Options]
211
indexterm:[Cluster Options,pe-warn-series-max]
210
indexterm:[pe-warn-series-max,Cluster Option]
211
indexterm:[Cluster,Option,pe-warn-series-max]
212
212
The number of PE inputs resulting in WARNINGs to save. Used when reporting problems.
214
214
| pe-input-series-max | -1 (all) |
215
indexterm:[pe-input-series-max Cluster Options]
216
indexterm:[Cluster Options,pe-input-series-max]
215
indexterm:[pe-input-series-max,Cluster Option]
216
indexterm:[Cluster,Option,pe-input-series-max]
217
217
The number of "normal" PE inputs to save. Used when reporting problems.
219
219
|=========================================================
221
221
You can always obtain an up-to-date list of cluster options, including
222
their default values, by running the pass:[<command>pengine
223
metadata</command>] command.
222
their default values, by running the `pengine
225
225
== Querying and Setting Cluster Options ==
227
indexterm:[Querying Cluster Options]
228
indexterm:[Setting Cluster Options]
229
indexterm:[Cluster Options,Querying]
230
indexterm:[Cluster Options,Setting]
227
indexterm:[Querying,Cluster Option]
228
indexterm:[Setting,Cluster Option]
229
indexterm:[Cluster,Querying Options]
230
indexterm:[Cluster,Setting Options]
232
232
Cluster options can be queried and modified using the
233
pass:[<command>crm_attribute</command>] tool. To get the current
233
`crm_attribute` tool. To get the current
234
234
value of +cluster-delay+, simply use:
236
pass:[<command>crm_attribute --attr-name cluster-delay --get-value</command>]
237
# crm_attribute --attr-name cluster-delay --get-value
238
239
which is more simply written as
240
pass:[<command>crm_attribute --get-value -n cluster-delay</command>]
242
# crm_attribute --get-value -n cluster-delay
242
244
If a value is found, you'll see a result like this:
244
pass:[<command> # crm_attribute --get-value -n cluster-delay</command>]
247
# crm_attribute --get-value -n cluster-delay
246
248
name=cluster-delay value=60s
249
250
However, if no value is found, the tool will display an error:
251
pass:[<command># crm_attribute --get-value -n clusta-deway</command>]
253
name=clusta-deway value=(null)
254
Error performing operation: The object/attribute does not exist
253
# crm_attribute --get-value -n clusta-deway`
254
name=clusta-deway value=(null)
255
Error performing operation: The object/attribute does not exist
257
257
To use a different value, eg. +30+, simply run:
259
pass:[<command>crm_attribute --attr-name cluster-delay --attr-value 30s</command>]
260
# crm_attribute --attr-name cluster-delay --attr-value 30s
261
262
To go back to the cluster's default value you can delete the value, for example with this command:
263
pass:[<command>crm_attribute --attr-name cluster-delay --delete-attr</command>]
265
# crm_attribute --attr-name cluster-delay --delete-attr
265
267
== When Options are Listed More Than Once ==
added
removed
doc/Pacemaker_Explained/en-US/Ch-Options.txt
