Installation guide

• Children must all stop cleanly before a parent may be stopped.
• For a resource to be considered in good health, all its children must be in good health.
2. Sibling Start Ordering and Resource Child Ordering
The Service resource determines the start order and the stop order of a child resource
according to whether it designates a child-type attribute for a child resource as follows:
• Designates child-type attribute (typed child resource) — If the Service resource designates a
child-type attribute for a child resource, the child resource is typed. The child-type attribute
explicitly determines the start and the stop order of the child resource.
• Does not designate child-type attribute (non-typed child resource) — If the Service resource
does not designate a child-type attribute for a child resource, the child resource is non-typed.
The Service resource does not explicitly control the starting order and stopping order of a
non-typed child resource. However, a non-typed child resource is started and stopped
according to its order in /etc/cluster.cluster.conf In addition, non-typed child resources
are started after all typed child resources have started and are stopped before any typed child
resources have stopped.
Note
The only resource to implement defined child resource type ordering is the
Service resource.
For more information about typed child resource start and stop ordering, refer to Section 2.1,
“Typed Child Resource Start and Stop Ordering”. For more information about non-typed child
resource start and stop ordering, refer to Section 2.2, “Non-typed Child Resource Start and Stop
Ordering”.
2.1. Typed Child Resource Start and Stop Ordering
For a typed child resource, the type attribute for the child resource defines the start order and
the stop order of each resource type with a number from 1 and 100; one value for start, and one
value for stop. The lower the number, the earlier a resource type starts or stops. For example,
Table D.1, “Child Resource Type Start and Stop Order” shows the start and stop values for
each resource type; Example D.2, “Resource Start and Stop Values: Excerpt from Service
Resource Agent, service.sh” shows the start and stop values as they appear in the Service
resource agent, service.sh. For the Service resource, all LVM children are started first,
followed by all File System children, followed by all Script children, and so forth.
Sibling Start Ordering and Resource Child
109