Pacemaker version on cluster node elected Designated Controller (DC)

Includes a hash which identifies the exact changeset the code was built from. Used for diagnostic purposes.

The messaging stack on which Pacemaker is currently running

Used for informational and diagnostic purposes.

An arbitrary name for the cluster

This optional value is mostly for users' convenience as desired in administration, but may also be used in Pacemaker configuration rules via the #cluster-name node attribute, and by higher-level tools and resource agents.

How long to wait for a response from other nodes during start-up

The optimal value will depend on the speed and load of your network and the type of switches used.

Polling interval to recheck cluster state and evaluate rules with date specifications

Pacemaker is primarily event-driven, and looks ahead to know when to recheck cluster state for failure timeouts and most time-based rules. However, it will also recheck the cluster after this amount of inactivity, to evaluate rules with date specifications and serve as a fail-safe for certain types of scheduler bugs. Allowed values: Zero disables polling, while positive values are an interval in seconds(unless other units are specified, for example "5min")

Maximum amount of system load that should be used by cluster nodes

The cluster will slow down its recovery process when the amount of system resources used (currently CPU) approaches this limit

Maximum number of jobs that can be scheduled per node (defaults to 2x cores)

How a cluster node should react if notified of its own fencing

A cluster node may receive notification of its own fencing if fencing is misconfigured, or if fabric fencing is in use that doesn't cut cluster communication. Allowed values are "stop" to attempt to immediately stop Pacemaker and stay stopped, or "panic" to attempt to immediately reboot the local node, falling back to stop on failure.

*** Advanced Use Only ***

Declare an election failed if it is not decided within this much time. If you need to adjust this value, it probably indicates the presence of a bug.

*** Advanced Use Only ***

Exit immediately if shutdown does not complete within this much time. If you need to adjust this value, it probably indicates the presence of a bug.

*** Advanced Use Only ***

If you need to adjust this value, it probably indicates the presence of a bug.

*** Advanced Use Only ***

If you need to adjust this value, it probably indicates the presence of a bug.

*** Advanced Use Only *** Enabling this option will slow down cluster recovery under all conditions

Delay cluster recovery for this much time to allow for additional events to occur. Useful if your configuration is sensitive to the order in which ping updates arrive.

How long to wait before we can assume nodes are safely down when watchdog-based self-fencing via SBD is in use

If nonzero, along with `have-watchdog=true` automatically set by the cluster, when fencing is required, watchdog-based self-fencing will be performed via SBD without requiring a fencing resource explicitly configured. If `stonith-watchdog-timeout` is set to a positive value, unseen nodes are assumed to self-fence within this much time. +WARNING:+ It must be ensured that this value is larger than the `SBD_WATCHDOG_TIMEOUT` environment variable on all nodes. Pacemaker verifies the settings individually on all nodes and prevents startup or shuts down if configured wrongly on the fly. It's strongly recommended that `SBD_WATCHDOG_TIMEOUT` is set to the same value on all nodes. If `stonith-watchdog-timeout` is set to a negative value, and `SBD_WATCHDOG_TIMEOUT` is set, twice that value will be used. +WARNING:+ In this case, it's essential (currently not verified by Pacemaker) that `SBD_WATCHDOG_TIMEOUT` is set to the same value on all nodes.

How many times fencing can fail before it will no longer be immediately re-attempted on a target

Author.