2. EL 7
  3. pacemaker
  4. pengine(7)

Scroll to navigation

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] [shutdown-lock=boolean] [shutdown-lock-limit=time] [stonith-enabled=boolean] [stonith-action=enum] [stonith-timeout=time] [have-watchdog=boolean] [concurrent-fencing=boolean] [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-base=integer] [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 [(null)]

Deprecated (use resource-stickiness in rsc_defaults instead)

is-managed-default = boolean [(null)]

Deprecated (use is-managed in rsc_defaults instead)

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

When set to TRUE, the cluster will immediately ban a resource from a node if it fails to start there. When FALSE, the cluster will instead check the resource's fail count against its migration-threshold.

enable-startup-probes = boolean [true]

Should the cluster check for active resources during startup

shutdown-lock = boolean [false]

Whether to lock resources to a cleanly shut down node

When true, resources active on a node when it is cleanly shut down are kept "locked" to that node (not allowed to run elsewhere) until they start again on that node after it rejoins (or for at most shutdown-lock-limit, if set). Stonith resources and Pacemaker Remote connections are never locked. Clone and bundle instances and the master role of promotable clones are currently never locked, though support could be added in a future release.

shutdown-lock-limit = time [0]

Do not lock resources to a cleanly shut down node longer than this

If shutdown-lock is true and this is set to a nonzero time duration, shutdown locks will expire after this much time has passed since the shutdown was initiated, even if the node has not rejoined.

stonith-enabled = boolean [true]

Failed nodes are STONITH'd

stonith-action = enum [reboot]

Action to send to STONITH device ('poweroff' is a deprecated alias for 'off')

Action to send to STONITH device ('poweroff' is a deprecated alias for 'off') Allowed values: reboot, off, poweroff

stonith-timeout = time [60s]

How long to wait for the STONITH action (reboot,on,off) to complete

have-watchdog = boolean [false]

Enable watchdog integration

Set automatically by the cluster if SBD is detected. User configured values are ignored.

concurrent-fencing = boolean [true]

Allow performing fencing operations in parallel

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 [0]

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 [(null)]

Deprecated (use 'timeout' in op_defaults instead)

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-base = integer [0]

The base score assigned to a node

Only used when node-health-strategy is set to progressive.

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.
12/15/2020 Pacemaker Configuration