24.7 Auto-Restart Restricted Resource

Many customers have taken to using CAA for more than just making an application highly available. Due to CAA's capability to periodically poll an application's state and take action if/when this occurs, why not use this functionality to automatically restart applications that may be multi-instance or even cluster-aware?

The implementation is straightforward with the key being in the "check" entry point. Unfortunately, we cannot detail how to implement a "check" entry point because determining an application's health is highly subjective and application-specific. We can, however, give you some guidelines.

If you have a multi-instance or distributed application, create resources for each instance.
Set the PLACEMENT to "restricted".
Set the HOSTING_MEMBERS attribute to the member on which to restrict the resource.
- If you are setting up multiple resources for a multi-instance or distributed application, set the HOSTING_MEMBERS attribute to one member per resource and do not duplicate.
If you want the resource restarted on cluster boot, regardless of its state when the cluster was shutdown, set the AUTO_START attribute to "1".
Set ACTIVE_PLACEMENT to "1".