FORCEDOWN - Configuring a Resource to be Automatically Shutdown

You can configure automation so that under certain circumstances, it will shut down a resource. This is done by creating ForceDown relationships from the resource to be stopped to the resource that will trigger the shutdown. The condition on the ForceDown relationship defines the circumstances when the shutdown is triggered. For example, ForceDown/WhenAssumedDownOrStopping will activate the forced shutdown if the target resource abends, is shut down, or is being shut down.

The shutdown request is injected at FORCE priority and overrides ANY operator request – including a FORCE start. This stop request is propagated normally over the dependency relationships and can end up affecting a large number of resources. It does not override any of the normal shutdown processing, so the resources involved will be shut down in an orderly sequence.

The ForceDown relationship does not contribute to a resource's stop or start dependencies. If you want automation to ensure that the resource is shut down before the one it has a ForceDown relationship to, you need to add an explicit automation sequence relationship, such as HasParent or MakeUnavailable/WhenAssumedDown between the two resources.

Once the forced shutdown is complete, the injected request will be removed. However, the resource will not be allowed to restart until the circumstances that triggered the forcedown have been resolved. So, if the forcedown was triggered by a WhenAssumedDown condition, the resources that were stopped as a result of it would not be allowed to restart until the resource that triggered the shutdown was in, at least, a Starting state.

The above is applicable when the resources have a start dependency with the resource that triggered the shutdown. If there is no start dependency, then the dependent resources will be able to restart immediately.