1PACEMAKER-CONTROLD(7)       Pacemaker Configuration      PACEMAKER-CONTROLD(7)
2
3
4

NAME

6       pacemaker-controld - controller properties
7

SYNOPSIS

9       [dc-version=string] [cluster-infrastructure=string] [dc-deadtime=time]
10       [cluster-recheck-interval=time] [load-threshold=percentage]
11       [node-action-limit=integer] [election-timeout=time]
12       [shutdown-escalation=time] [join-integration-timeout=time]
13       [join-finalization-timeout=time] [transition-delay=time]
14       [stonith-watchdog-timeout=time] [stonith-max-attempts=integer]
15

DESCRIPTION

17       Cluster properties used by Pacemaker's controller, formerly known as
18       crmd
19

SUPPORTED PARAMETERS

21       dc-version = string [none]
22           Version of Pacemaker on the cluster's DC.
23
24           Includes the hash which identifies the exact changeset it was built
25           from. Used for diagnostic purposes.
26
27       cluster-infrastructure = string [corosync]
28           The messaging stack on which Pacemaker is currently running.
29
30           Used for informational and diagnostic purposes.
31
32       dc-deadtime = time [20s]
33           How long to wait for a response from other nodes during startup.
34
35           The "correct" value will depend on the speed/load of your network
36           and the type of switches used.
37
38       cluster-recheck-interval = time [15min]
39           Polling interval for time based changes to options, resource
40           parameters and constraints.
41
42           The Cluster is primarily event driven, however the configuration
43           can have elements that change based on time. To ensure these
44           changes take effect, we can optionally poll the cluster's status
45           for changes. Allowed values: Zero disables polling. Positive values
46           are an interval in seconds (unless other SI units are specified.
47           eg. 5min)
48
49       load-threshold = percentage [80%]
50           The maximum amount of system resources that should be used by nodes
51           in the cluster
52
53           The cluster will slow down its recovery process when the amount of
54           system resources used (currently CPU) approaches this limit
55
56       node-action-limit = integer [0]
57           The maximum number of jobs that can be scheduled per node. Defaults
58           to 2x cores
59
60       election-timeout = time [2min]
61           *** Advanced Use Only ***.
62
63           If need to adjust this value, it probably indicates the presence of
64           a bug.
65
66       shutdown-escalation = time [20min]
67           *** Advanced Use Only ***.
68
69           If need to adjust this value, it probably indicates the presence of
70           a bug.
71
72       join-integration-timeout = time [3min]
73           *** Advanced Use Only ***
74
75           If need to adjust this value, it probably indicates the presence of
76           a bug
77
78       join-finalization-timeout = time [30min]
79           *** Advanced Use Only ***
80
81           If you need to adjust this value, it probably indicates the
82           presence of a bug
83
84       transition-delay = time [0s]
85           *** Advanced Use Only *** Enabling this option will slow down
86           cluster recovery under all conditions
87
88           Delay cluster recovery for the configured interval to allow for
89           additional/related events to occur. Useful if your configuration is
90           sensitive to the order in which ping updates arrive.
91
92       stonith-watchdog-timeout = time [(null)]
93           How long to wait before we can assume nodes are safely down
94
95       stonith-max-attempts = integer [10]
96           How many times stonith can fail before it will no longer be
97           attempted on a target
98

AUTHOR

100       Andrew Beekhof <andrew@beekhof.net>
101           Author.
102
103
104
105Pacemaker Configuration           07/25/2019             PACEMAKER-CONTROLD(7)
Impressum