Option | Default | Description |
---|---|---|
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. |
no-quorum-policy | stop |
What to do when the cluster does not have quorum. Allowed values:
|
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, poweroff. |
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-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. |
[5] This will be described later in the section on Chapter 8, Rules where we will show how to have the cluster use different sets of options during working hours (when downtime is usually to be avoided at all costs) than it does during the weekends (when resources can be moved to the their preferred hosts without bothering end users)