Appendix E. Cluster Service Resource Check and Failover Timeout
rgmanagermonitors the status of cluster resources, and how to modify the status check interval. The appendix also describes the
__enforce_timeoutsservice parameter, which indicates that a timeout for an operation should cause a service to fail.
/etc/cluster/cluster.conf. For a comprehensive list and description of
cluster.confelements and attributes, refer to the cluster schema at
/usr/share/system-config-cluster/misc/cluster.ng, and the annotated schema at
E.1. Modifying the Resource Status Check Interval
rgmanagerchecks the status of individual resources, not whole services. (This is a change from
clumanageron Red Hat Enterprise Linux 3, which periodically checked the status of the whole service.) Every 10 seconds, rgmanager scans the resource tree, looking for resources that have passed their "status check" interval.
cluster.conffile using the special
<action name="status" depth="*" interval="10" />
cluster.conffile. For example, if you had a file system resource for which you wanted to override the status check interval you could specify the file system resource in the
cluster.conffile as follows:
<fs name="test" device="/dev/sdb3"> <action name="status" depth="*" interval="10" /> <nfsexport...> </nfsexport> </fs>
depthis set to
*, which indicates that these values should be used for all depths. The result is that the
testfile system is checked at the highest-defined depth provided by the resource-agent (in this case, 20) every 10 seconds.