Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

crm_failcount(8) [suse man page]

CRM_FAILCOUNT(8)						  [FIXME: manual]						  CRM_FAILCOUNT(8)

NAME

       crm_failcount - manipulate the failcount attribute on a given resource

SYNOPSIS

	   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

DESCRIPTION

       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.

OPTIONS

       --help, -?
	   Print a help message.

       --verbose, -V
	   Turn on debug information.

	       Note
	       Increase the level of verbosity by providing additional instances.

       --quiet, -Q
	   When doing an attribute query using -G, print just the value to stdout. Use this option with -G.

       --get-value, -G
	   Retrieve rather than set the preference.

       --delete-attr, -D
	   Specify the attribute to delete.

       --attr-value string, -v string
	   Specify the value to use. This option is ignored when used with -G.

       --node-uuid node_uuid, -u node_uuid
	   Specify the UUID of the node to change.

       --node-uname node_uname, -U node_uname
	   Specify the uname of the node to change.

       --resource-id resource name, -r resource name
	   Specify the name of the resource on which to operate.

EXAMPLES

       Reset the failcount for the resource myrsc on the node node1:

	       crm_failcount -D -U node1 -r my_rsc

       Query the current failcount for the resource myrsc on the node node1:

	       crm_failcount -G -U node1 -r my_rsc

FILES

       /var/lib/heartbeat/crm/cib.xml--the CIB (minus status section) on disk. Editing this file directly is strongly discouraged.

SEE ALSO

       ???, ???, and the Linux High Availability FAQ Web site[1]

AUTHOR

       crm_failcount was written by Andrew Beekhof.

NOTES

	1. Linux High Availability FAQ Web site
	   http://www.linux-ha.org/v2/faq/forced_failover

[FIXME: source] 						    07/05/2010							  CRM_FAILCOUNT(8)

Check Out this Related Man Page

OCF_HEARTBEAT_DUMMY(7)						OCF resource agents					    OCF_HEARTBEAT_DUMMY(7)

NAME

       ocf_heartbeat_Dummy - Example stateless resource agent

SYNOPSIS

       Dummy [start | stop | monitor | reload | migrate_to | migrate_from | meta-data | validate-all]

DESCRIPTION

       This is a Dummy Resource Agent. It does absolutely nothing except keep track of whether its running or not. Its purpose in life is for
       testing and to serve as a template for RA writers. NB: Please pay attention to the timeouts specified in the actions section below. They
       should be meaningful for the kind of resource the agent manages. They should be the minimum advised timeouts, but they shouldn't/cannot
       cover _all_ possible resource instances. So, try to be neither overly generous nor too stingy, but moderate. The minimum timeouts should
       never be below 10 seconds.

SUPPORTED PARAMETERS

       state
	   Location to store the resource state in. (optional, string, default /var/run/resource-agents/Dummy-{OCF_RESOURCE_INSTANCE}.state)

SUPPORTED ACTIONS

       This resource agent supports the following actions (operations):

       start
	   Starts the resource. Suggested minimum timeout: 20.

       stop
	   Stops the resource. Suggested minimum timeout: 20.

       monitor
	   Performs a detailed status check. Suggested minimum timeout: 20. Suggested interval: 10.

       reload
	   Suggested minimum timeout: 20.

       migrate_to
	   Executes steps necessary for migrating the resource to the node. Suggested minimum timeout: 20.

       migrate_from
	   Executes steps necessary for migrating the resource away from the node. Suggested minimum timeout: 20.

       meta-data
	   Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5.

       validate-all
	   Performs a validation of the resource configuration. Suggested minimum timeout: 20.

EXAMPLE

       The following is an example configuration for a Dummy resource using the crm(8) shell:

	   primitive example_Dummy ocf:heartbeat:Dummy 

	     meta allow-migrate="true" 
	     op monitor timeout="20" interval="10" depth="0"

SEE ALSO

       http://www.linux-ha.org/wiki/Dummy_(resource_agent)

AUTHOR

       Linux-HA contributors (see the resource agent source for information about individual authors)

resource-agents 1.0.3						    07/05/2010						    OCF_HEARTBEAT_DUMMY(7)
Man Page