Chapter 4. Configuring and Managing Cluster Resources / 4.6. Configuring Resource Monitoring | ||||
|---|---|---|---|---|
 | 4.5. Specifying Resource Failback Nodes (Resource Stickiness) | 4.7. Starting a New Cluster Resource |  | |
Chapter 4. Configuring and Managing Cluster Resources / 4.6. Configuring Resource Monitoring | ||||
|---|---|---|---|---|
| 4.5. Specifying Resource Failback Nodes (Resource Stickiness) | 4.7. Starting a New Cluster Resource | | |
Although Heartbeat can detect a node failure, it also has the ability to detect when an individual resource on a node has failed. If you want Heartbeat to ensure that a resource is running, you must configure resource monitoring for that resource. Resource monitoring consists of specifying a timeout and/or start delay value, and an interval. The interval tells Heartbeat how often it should check the resource status.
To configure resource monitoring:
Start the HA Management Client and log in to the cluster as described in Section 4.1, “Graphical HA Management Client”.
Select the resource, click the tab, then click .
Select as the operation name.
Add the desired values in the , , and fields, and a description if desired.
Click , then click to start the monitoring operation.
If you do not configure resource monitoring, resource failures after a successful start will not be communicated, and the cluster will always show the resource as healthy.
If the resource monitor detects a failure, the following actions will take place:
Log file messages will be generated
The failure will be reflected in the hb_gui and crm_mon tools, and in the CIB status section
The cluster will initiate noticeable recovery actions which may include stopping the resource to repair the failed state and restarting the resource locally or on another node. The resource also may not be restarted at all, depending on the configuration and state of the cluster.
