Chapter 5. Manual Configuration of a Cluster / 5.4. Configuring CRM Options | ||||
|---|---|---|---|---|
 | 5.3. Configuring Constraints | Policy Engine |  | |
Chapter 5. Manual Configuration of a Cluster / 5.4. Configuring CRM Options | ||||
|---|---|---|---|---|
| 5.3. Configuring Constraints | Policy Engine | | |
The CRM options define the global behavior of a cluster. In
principle, the default values should be acceptable for many
environments, but if you want to use special services, like
STONITH devices, you must inform the cluster about this. All
options of crm_config are made with
nvpair and are added to
cib.xml. For example, to change the
cluster-delay from its default value of
60s to 120s, use the
following configuration:
<cluster_property_set>
<attributes>
<nvpair id="1" name="cluster-delay" value="120s"/>
</attributes>
</cluster_property_set> Write this information to a file and load it to the cluster
with the command cibadmin -C -o crm_config -x
filename. The following
is an overview of all available configuration options:
cluster-delay (interval, default=60s) This option used to be known as
transition_idle_timeout. If no activity
is recorded in this time, the transition is deemed failed as
are all sent actions that have not yet been confirmed
complete. If any operation initiated has an explicit higher
time-out, the higher value applies.
symmetric_cluster (boolean,
default=TRUE)If true, resources are permitted to run anywhere by default. Otherwise, explicit constraints must be created to specify where they can run.
stonith_enabled (boolean,
default=FALSE)If true, failed nodes are fenced.
no_quorum_policy (enum, default=stop)ignore
Pretend to have quorum.
freeze
Do not start any resources not currently in the partition. Resources in the partition may be moved to another node within the partition. Fencing is disabled.
stop
Stop all running resources in the partition. Fencing is disabled.
default_resource_stickiness (integer,
default=0)Select whether resources should prefer to run on the existing node or be moved to a “better” one?
0
Resources are placed optimally in the system.
This may mean they are moved when a
“better” or less-loaded node becomes
available. This option is almost equivalent to
auto_failback on except that the
resource may be moved to nodes other than the one on
which it was previously active.
value > 0
Resources prefer to remain in their current location but may be moved if a more suitable node is available. Higher values indicate a stronger preference for resources to stay where they are.
value < 0
Resources prefer to move away from their current location. Higher absolute values indicate a stronger preference for resources to be moved.
INFINITY
Resources always remain in their current
locations until forced off because the node is no
longer eligible to run the resource (node shutdown,
node standby, or configuration change). This option is
almost equivalent to auto_failback
off except that the resource may be moved to other
nodes than the one on which it was previously active.
-INFINITY
Resources always move away from their current location.
is_managed_default (boolean,
default=TRUE)Unless the resource's definition says otherwise:
TRUE
Resources are started, stopped, monitored, and moved as necessary.
FALSE
Resources are not started if stopped, stopped if started, or have any recurring actions scheduled.
stop_orphan_resources (boolean,
default=TRUE)If a resource is found for which there is no definition:
TRUE
Stop the resource.
FALSE
Ignore the resource.
This mostly affects the CRM's behavior when a resource is deleted by an administrator without it first being stopped.
stop_orphan_actions (boolean,
default=TRUE)If a recurring action is found for which there is no definition:
TRUE
Stop the action.
FALSE
Ignore the action.
All available options to the crm_config
are summarized in Policy Engine(7).
