 | ||
| VCS behavior diagrams | ||
|---|---|---|
| Prev | Controlling VCS behavior | Next |
This section describes the default functionality of VCS when resources fault. The illustration displays the symbols used in this section.
Click the thumbnail above to view full-sized image.
The service group in the following example has five resources, of which resource R1 is configured as a critical resource.
Click the thumbnail above to view full-sized image.
When resource R2 faults, the fault is propagated up the dependency tree to resource R1. When the critical resource R1 goes offline, VCS must fault the service group and fail it over elsewhere in the cluster. VCS takes other resources in the service group offline in the order of their dependencies. After taking resources R3, R4, and R5 offline, VCS fails over the service group to another node.
The service group in the following example does not have any critical resources.
Click the thumbnail above to view full-sized image.
When resource R2 faults, the engine propagates the failure up the dependency tree. Neither resource R1 nor resource R2 are critical, so the fault does not result in the tree going offline or in service group failover.
In the following example, when a command is issued to bring the service group online, resource R2 fails to come online.
Click the thumbnail above to view full-sized image.
VCS calls the Clean function for resource R2 and propagates the fault up the dependency tree. Resource R1 is set to critical, so the service group is taken offline and failed over to another node in the cluster.