3.3.2. Special node attributes

⁠3.3.2. Special node attributes

Certain node attributes have special meaning to the cluster.

Node attribute names beginning with # are considered reserved for these special attributes. Some special attributes do not start with #, for historical reasons.

Certain special attributes are set automatically by the cluster, should never be modified directly, and can be used only within rules; these are listed under Section 8.2, “Node Attribute Expressions”.

For true/false values, the cluster considers a value of "1", "y", "yes", "on", or "true" (case-insensitively) to be true, "0", "n", "no", "off", "false", or unset to be false, and anything else to be an error.

⁠

Table 3.1. Node attributes with special significance

Name	Description
`fail-count-*`	Attributes whose names start with `fail-count-` are managed by the cluster to track how many times particular resource operations have failed on this node. These should be queried and cleared via the `crm_failcount` or `crm_resource --cleanup` commands rather than directly.
`last-failure-*`	Attributes whose names start with `last-failure-` are managed by the cluster to track when particular resource operations have most recently failed on this node. These should be cleared via the `crm_failcount` or `crm_resource --cleanup` commands rather than directly.
`maintenance`	Similar to the `maintenance-mode` cluster option, but for a single node. If true, resources will not be started or stopped on the node, resources and individual clone instances running on the node will become unmanaged, and any recurring operations for those will be cancelled.
`probe_complete`	This is managed by the cluster to detect when nodes need to be reprobed, and should never be used directly.
`resource-discovery-enabled`	If the node is a remote node, fencing is enabled, and this attribute is explicitly set to false (unset means true in this case), resource discovery (probes) will not be done on this node. This is highly discouraged; the `resource-discovery` location constraint property is preferred for this purpose.
`shutdown`	This is managed by the cluster to orchestrate the shutdown of a node, and should never be used directly.
`site-name`	If set, this will be used as the value of the `#site-name` node attribute used in rules. (If not set, the value of the `cluster-name` cluster option will be used as `#site-name` instead.)
`standby`	If true, the node is in standby mode. This is typically set and queried via the `crm_standby` command rather than directly.
`terminate`	If the value is true or begins with any nonzero number, the node will be fenced. This is typically set by tools rather than directly.
`#digests-*`	Attributes whose names start with `#digests-` are managed by the cluster to detect when unfencing needs to be redone, and should never be used directly.
`#node-unfenced`	When the node was last unfenced (as seconds since the epoch). This is managed by the cluster and should never be used directly.

Warning

Restarting pacemaker on a node that is in single-node maintenance mode will likely lead to undesirable effects. If maintenance is set as a transient attribute, it will be erased when pacemaker is stopped, which will immediately take the node out of maintenance mode and likely get it fenced. Even if permanent, if pacemaker is restarted, any resources active on the node will have their local history erased when the node rejoins, so the cluster will no longer consider them running on the node and thus will consider them managed again, leading them to be started elsewhere. This behavior might be improved in a future release.