crm_failcount - manipulate the failcount attribute on a given resource
crm_failcount [-?|-V] -D -u|-U node -r resource
crm_failcount [-?|-V] -G -u|-U node -r resource
crm_failcount [-?|-V] -v string -u|-U node -r resource
Heartbeat implements a sophisticated method to compute and force failover of a resource to another node in case that resource tends to fail on the current node. A resource carries a resource_stickiness attribute to determine how much it prefers to run on a certain node. It also carries a resource_failure_stickiness that determines the threshold at which the resource should failover to another node.
The failcount attribute is added to the resource and increased on resource monitoring failure. The value of failcount multiplied by the value of resource_failure_stickiness determines the failover score of this resource. If this number exceeds the preference set for this resource, the resource is moved to another node and not run again on the original node until the failure count is reset.
The crm_failcount command queries the number of failures per resource on a given node. This tool can also be used to reset the failcount, allowing the resource to run again on nodes where it had failed too often.
Print a help message.
Turn on debug information.
NOTE:Increase the level of verbosity by providing additional instances.
When doing an attribute query using -G, print just the value to stdout. Use this option with -G.
Retrieve rather than set the preference.
Specify the attribute to delete.
For advanced users only. Identifies the id attribute.
Specify the value to use. This option is ignored when used with -G.
Specify the UUID of the node to change.
Specify the uname of the node to change.
Specify the name of the resource on which to operate.
For advanced users only.
crm_failcount -D -U node1 -r my_rsc
crm_failcount -G -U node1 -r my_rsc
/var/lib/heartbeat/crm/cib.xml—the CIB (minus status section) on disk. Editing this file directly is strongly discouraged.
crm_failcount was written by Andrew Beekhof.