[그림Figure] 그룹 시작/종료시 의존 관계에 있는 리소스들의 온라인/오프라인 순서Online/Offline Sequence of Dependent Resources When Starting or Terminating a Group

Dependency Configuration

define this dependency among resources, configure this link in the ‘Resource Dependency’ view.

...

 In MCCS, you can configure the dependency relationship of resources by using a tree.
From the above screen, we can find out about the dependency relationship among resources.
The network address resource as a parent depends on the network card NIC resource as its child. The complex app resource as a parent depends on the network address resource as its child.
MCCS performs a failover on a group basis. Thus, all the resources within a group should be connected in this dependency relationship and they need to be put into a single group before we can provide meaningful service.
If we set two resources as a parent and an child, we can see it as two vertical levels. The max level can be checked in the 'MaxDependencyLevel' value in the group attribute menu.

...

 Following are the general cases of dependency.

Network

...

Interface card(NIC) Resource, Network Address Resource

 Before assigning an IP address to the network address resource, you need to first have a physical network card. Without a network card, you cannot assign an IP address. If you set the network card NIC resource as an child and the network address resource as a parent, it will check whether the network card is normal when the network address resources tries to go online. 

...

 Many applications record data in a disk or storage. Thus, applications must depend on disks in the dependency relationship.
If you use the DB, you need to designate the disk to record data in. Thus, for the DB, you must set the dependency relationship where the DB as a parent depends on the disk as a child.
If a client needs an IP address to access the DB, you must set the network address as an child and the DB as a parent. Based on this dependency relationship, when a group goes online in MCCS, first check the network address resource and confirm whether the disk are unlocked properly before running the DB.
Thus the DB should be set to depend on both the network address resource and the disk resource.
We can provide the following configurations based on the dependency relationships discussed so far.

 

...

...

[Figure] Example of Failure Occur 1

1. As a failure is occurred at resource r2, resource r1 will be taken offline. (Since resource r1 depends on resource r2 which is failed, resource r1 may cannot be online properly.)
2. Since resource r1 has critical attribute, resource r3 and a4 will be taken offline in order to failover the group.
3. As a result, resource r2 is considered as failure and all resources in the group will be taken offline

...

[Figure] Example of Failure Occur 2

1. Resource r1 which is not critical is online status.
2. When resource r2 get failed, resource r1 will be taken offline because it dependent on resource r2.
3. As r1 resource is not critical, group failover will be not performed. Therefore, the group will be partial online status.

...

[Figure] Example of Failure Occur 3

1. On the assumption that the value of RestartLimit is 1 for resource r2, the first failure has occurred.
2. MCCS will bring online resource r2 again as the value of RestartLimit. 
   At this time, resource r1 which depends on resource r2 will be taken offline.
3. resource r2 restart.
4. resource r1 online.
5. When another failure occurs on resource r2, all of the resource will be taken offline from resource r1 to r3 by order.
6. Resource r3 will be taken offline.
7. As a result, resource r2 is considered as failure and all resources in the group is offline status in the node.

...