|
batch-limit
|
30
|
The number of jobs that the TE is allowed to execute in parallel. The "correct" value will depend on the speed and load of your network and cluster nodes.
|
|
migration-limit
|
-1 (unlimited)
|
The number of migration jobs that the TE is allowed to execute in parallel on a node.
|
|
no-quorum-policy
|
stop
|
What to do when the cluster does not have quorum. Allowed values:
* ignore - continue all resource management
* freeze - continue resource management, but don’t recover resources from nodes not in the affected partition
* stop - stop all resources in the affected cluster partition
* suicide - fence all nodes in the affected cluster partition
|
|
symmetric-cluster
|
TRUE
|
Can all resources run on any node by default?
|
|
stonith-enabled
|
TRUE
|
Should failed nodes and nodes with resources that can’t be stopped be shot? If you value your data, set up a STONITH device and enable this.
If true, or unset, the cluster will refuse to start resources unless one or more STONITH resources have been configured also.
|
|
stonith-action
|
reboot
|
Action to send to STONITH device. Allowed values: reboot, off. The value poweroff is also allowed, but is only used for legacy devices.
|
|
cluster-delay
|
60s
|
Round trip delay over the network (excluding action execution). The "correct" value will depend on the speed and load of your network and cluster nodes.
|
|
stop-all-resources
|
FALSE
|
Should the cluster stop all resources
|
|
resources-orphan-resources
|
TRUE
|
Should deleted resources be stopped?
|
|
stop-orphan-actions
|
TRUE
|
Should deleted actions be cancelled?
|
|
start-failure-is-fatal
|
TRUE
|
When set to FALSE, the cluster will instead use the resource’s failcount and value for resource-failure-stickiness.
|
|
pe-error-series-max
|
-1 (all)
|
The number of PE inputs resulting in ERRORs to save. Used when reporting problems.
|
|
pe-warn-series-max
|
-1 (all)
|
The number of PE inputs resulting in WARNINGs to save. Used when reporting problems.
|
|
pe-input-series-max
|
-1 (all)
|
The number of "normal" PE inputs to save. Used when reporting problems.
|
|
default-resource-stickiness
|
0
|
|
|
is-managed-default
|
TRUE
|
|
|
maintenance-mode
|
FALSE
|
Should the cluster monitor resources and start/stop them as required
|
|
stonith-timeout
|
60s
|
How long to wait for the STONITH action to complete
|
|
default-action-timeout
|
20s
|
|
|
dc-deadtime
|
20s
|
How long to wait for a response from other nodes during startup.
The "correct" value will depend on the speed/load of your network and the type of switches used.
|
|
cluster-recheck-interval
|
15min
|
Polling interval for time based changes to options, resource parameters and constraints.
The Cluster is primarily event driven, however the configuration can have elements that change based on time. To ensure these changes take effect, we can optionally poll the cluster’s status for changes.
Allowed values: Zero disables polling. Positive values are an interval in seconds (unless other SI units are specified. eg. 5min)
|
|
election-timeout
|
2min
|
If need to adjust this value, it probably indicates the presence of a bug.
|
|
shutdown-escalation
|
20min
|
If need to adjust this value, it probably indicates the presence of a bug.
|
|
crmd-integration-timeout
|
3min
|
If need to adjust this value, it probably indicates the presence of a bug.
|
|
crmd-finalization-timeout
|
30min
|
If need to adjust this value, it probably indicates the presence of a bug.
|
|
crmd-transition-delay
|
|
Advanced Use Only Enabling this option will slow down cluster recovery under all conditions.
Delay cluster recovery for the configured interval to allow for additional/related events to occur. Useful if your configuration is sensitive to the order in which ping updates arrive.
|
