GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages
PACEMAKER-SCHEDULER(7) Pacemaker Configuration PACEMAKER-SCHEDULER(7)

pacemaker-schedulerd - scheduler properties

[ no-quorum-policy=enum] [symmetric-cluster=boolean] [maintenance-mode=boolean] [ start-failure-is-fatal=boolean] [enable-startup-probes=boolean] [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] [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]

Cluster properties used by Pacemaker's scheduler, formerly known as pengine

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
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
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 [false]
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
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 executor 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 scheduler inputs resulting in ERRORs to save
Zero to disable, -1 to store unlimited
pe-warn-series-max = integer [5000]
The number of scheduler inputs resulting in WARNINGs to save
Zero to disable, -1 to store unlimited
pe-input-series-max = integer [4000]
The number of other scheduler 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

Andrew Beekhof <andrew@beekhof.net>
Author.
01/02/2019 Pacemaker Configuration

Search for    or go to Top of page |  Section 7 |  Main Index

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with ManDoc.