Resource_dependencies_restart Not Working As Expected (5041013)

Problem Summary: The Resource_dependencies_restart resource property does not behave as expected when a resource declares an any node inter-resource–group restart dependency upon a scalable mode resource. Most data services are unaffected.

• Background on inter-resource–group dependencies and restart dependencies:

  With the inter-resource–group dependencies feature in Sun Cluster 3.1 9/04, Sun Cluster software supports resource dependencies that can cross resource group boundaries. Sun Cluster software also supports a new type of resource dependency, the restart dependency. If the dependent resource is online, the restart dependency causes the dependent resource to be restarted automatically when the depended-on resource starts.

• Background on local node vs. any node dependencies:

  If resource r1 in group RG1 has a dependency on r2 in RG2, and if RG1 has a positive affinity for RG2, and if both RG1 and RG2 are starting or stopping simultaneously on the same node, then the dependency of r1 on r2 is a local node dependency. For example, while starting RG1 and RG2 on the same node, r1 waits for r2 to start on that node before r1 starts on that same node. The state of r2 on other nodes does not influence when r1 starts.

  However, if RG1 does not declare a positive affinity for RG2, or if there is a weak positive affinity, but the resource groups start on different nodes, then the dependency of r1 on r2 is an any node dependency. This dependency means that r1 starts as soon as r2 has started on any node.

• Description of Problem:

  The problem arises when resource group RG2 is a scalable mode (i.e. multi-mastered) resource group, and the dependency of r1 on r2 is an any node restart dependency. r1 is restarted every time that any instance of r2 starts. r1 should be restarted only upon the first instance of r2 that starts.

Workaround: The current behavior of restart dependencies will change as described above, when this bug is fixed. Do not develop code or administrative procedures that depend upon the current incorrect behavior.