Scalable RG: unexpected behaviour
I have a scalable RG managing a JBOSS process on 2 nodes.
For test purpose I kill (SIGTERM) the JBOSS process on one node expecting the cluster framework to restart it. I notices on the web console that the node disapears from the "current primaries" list of the scalable RG.
I can see in the cluster logs that the monitoring of the resource is working well and returns a failure (return code 100), but the cluster framework is NOT restarting the process.
The only way to restart the JBOSS process is to add again the node to the "current primaries" of the scalable RG which needs a user action.