hard

Define a hard start dependency for a resource if another resource must be running before the dependent resource can start. For example, if resource A has a hard start dependency on resource B, then resource B must be running before resource A can start.

You can configure the hard start dependency with the following constraints:

• START_DEPENDENCIES=hard(global:resourceB)

  By default, resources A and B must be located on the same server (collocated). Use the global modifier to specify that resources need not be collocated. For example, if resource A has a hard(global:resourceB) start dependency on resource B, then, if resource B is running on any node in the cluster, resource A can start.

• START_DEPENDENCIES=hard(intermediate:resourceB)

  Use the intermediate modifier to specify that the dependent resource can start if a resource on which it depends is in either the ONLINE or INTERMEDIATE state.

• START_DEPENDENCIES=hard(type:resourceB.type)

  Use the type modifier to specify whether the hard start dependency acts on a particular resource or a resource type. For example, if you specify that resource A has a hard start dependency on the resourceB.type type, then if any resource of the resourceB.type type is running, resource A can start.

• START_DEPENDENCIES=hard(uniform:resourceB)

  Use the uniform modifier to attempt to start all instances of resource B, but only one instance, at least must start to satisfy the dependency.

• START_DEPENDENCIES=hard(resourceB, intermediate:resourceC, intermediate:global:type:resourceC.type)

  You can combine modifiers and specify multiple resources in the START_DEPENDENCIES resource attribute.

  Note:

  Separate modifier clauses with commas. The type modifier clause must always be the last modifier clause in the list and the type modifier must always directly precede the type.