CRM DAEMON(7) Pacemaker Configuration CRM DAEMON(7)NAME
crmd - CRM Daemon Options
SYNOPSIS
[dc-version=string] [cluster-infrastructure=string] [dc-deadtime=time] [cluster-recheck-interval=time] [election-timeout=time]
[shutdown-escalation=time] [crmd-integration-timeout=time] [crmd-finalization-timeout=time] [crmd-transition-delay=time]
[expected-quorum-votes=integer]
DESCRIPTION
This is a fake resource that details the options that can be configured for the CRM Daemon.
SUPPORTED PARAMETERS
dc-version = string [none]
Version of Pacemaker on the cluster's DC.
Includes the hash which identifies the exact Mercurial changeset it was built from. Used for diagnostic purposes.
cluster-infrastructure = string [heartbeat]
The messaging stack on which Pacemaker is currently running.
Used for informational and diagnostic purposes.
dc-deadtime = time [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 = time [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 = time [2min]
*** Advanced Use Only ***.
If need to adjust this value, it probably indicates the presence of a bug.
shutdown-escalation = time [20min]
*** Advanced Use Only ***.
If need to adjust this value, it probably indicates the presence of a bug.
crmd-integration-timeout = time [3min]
*** Advanced Use Only ***.
If need to adjust this value, it probably indicates the presence of a bug.
crmd-finalization-timeout = time [30min]
*** Advanced Use Only ***.
If you need to adjust this value, it probably indicates the presence of a bug.
crmd-transition-delay = time [0s]
*** 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.
expected-quorum-votes = integer [2]
The number of nodes expected to be in the cluster
Used to calculate quorum in openais based clusters.
AUTHOR
Andrew Beekhof <andrew@beekhof.net>
Author.
Pacemaker Configuration 04/17/2012 CRM DAEMON(7)
Check Out this Related Man Page
POLICY ENGINE(7) Pacemaker Configuration POLICY ENGINE(7)NAME
pengine - Policy Engine Options
SYNOPSIS
[no-quorum-policy=enum] [symmetric-cluster=boolean] [default-resource-stickiness=integer] [is-managed-default=boolean]
[maintenance-mode=boolean] [start-failure-is-fatal=boolean] [enable-startup-probes=boolean] [stonith-enabled=boolean] [stonith-action=enum]
[stonith-timeout=time] [startup-fencing=boolean] [cluster-delay=time] [batch-limit=integer] [migration-limit=integer]
[default-action-timeout=time] [stop-all-resources=boolean] [stop-orphan-resources=boolean] [stop-orphan-actions=boolean]
[remove-after-stop=boolean] [pe-error-series-max=integer] [pe-warn-series-max=integer] [pe-input-series-max=integer]
[node-health-strategy=enum] [node-health-green=integer] [node-health-yellow=integer] [node-health-red=integer] [placement-strategy=enum]
DESCRIPTION
This is a fake resource that details the options that can be configured for the Policy Engine.
SUPPORTED PARAMETERS
no-quorum-policy = enum [stop]
What to do when the cluster does not have quorum
What to do when the cluster does not have quorum Allowed values: stop, freeze, ignore, suicide
symmetric-cluster = boolean [true]
All resources can run anywhere by default
default-resource-stickiness = integer [0]
is-managed-default = boolean [true]
Should the cluster start/stop resources as required
maintenance-mode = boolean [false]
Should the cluster monitor resources and start/stop them as required
start-failure-is-fatal = boolean [true]
Always treat start failures as fatal
This was the old default. However when set to FALSE, the cluster will instead use the resource's failcount and value for
resource-failure-stickiness
enable-startup-probes = boolean [true]
Should the cluster check for active resources during startup
stonith-enabled = boolean [true]
Failed nodes are STONITH'd
stonith-action = enum [reboot]
Action to send to STONITH device
Action to send to STONITH device Allowed values: reboot, poweroff, off
stonith-timeout = time [60s]
How long to wait for the STONITH action to complete
startup-fencing = boolean [true]
STONITH unseen nodes
Advanced Use Only! Not using the default is very unsafe!
cluster-delay = time [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.
batch-limit = integer [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 = integer [-1]
The number of migration jobs that the TE is allowed to execute in parallel on a node
default-action-timeout = time [20s]
How long to wait for actions to complete
stop-all-resources = boolean [false]
Should the cluster stop all active resources (except those needed for fencing)
stop-orphan-resources = boolean [true]
Should deleted resources be stopped
stop-orphan-actions = boolean [true]
Should deleted actions be cancelled
remove-after-stop = boolean [false]
Remove resources from the LRM after they are stopped
Always set this to false. Other values are, at best, poorly tested and potentially dangerous.
pe-error-series-max = integer [-1]
The number of PE inputs resulting in ERRORs to save
Zero to disable, -1 to store unlimited.
pe-warn-series-max = integer [5000]
The number of PE inputs resulting in WARNINGs to save
Zero to disable, -1 to store unlimited.
pe-input-series-max = integer [4000]
The number of other PE inputs to save
Zero to disable, -1 to store unlimited.
node-health-strategy = enum [none]
The strategy combining node attributes to determine overall node health.
Requires external entities to create node attributes (named with the prefix '#health') with values: 'red', 'yellow' or 'green'. Allowed
values: none, migrate-on-red, only-green, progressive, custom
node-health-green = integer [0]
The score 'green' translates to in rsc_location constraints
Only used when node-health-strategy is set to custom or progressive.
node-health-yellow = integer [0]
The score 'yellow' translates to in rsc_location constraints
Only used when node-health-strategy is set to custom or progressive.
node-health-red = integer [-INFINITY]
The score 'red' translates to in rsc_location constraints
Only used when node-health-strategy is set to custom or progressive.
placement-strategy = enum [default]
The strategy to determine resource placement
The strategy to determine resource placement Allowed values: default, utilization, minimal, balanced
AUTHOR
Andrew Beekhof <andrew@beekhof.net>
Author.
Pacemaker Configuration 06/10/2014 POLICY ENGINE(7)