Note the following points when starting and stopping each resource:
The information, on which only some resources under userApplication are being started, is synchronized on all the nodes where this userApplication operates. Therefore, if an application is switched automatically while only some resources are being started, the only resource that was started on the source node can be started on the remote node.
If some resource becomes Online unexpectedly while the userApplication is partially Online, the userApplication remains in Online state (does not become Inconsistent state). If an application is switched automatically in this state, the unexpected started resource cannot become Online on the remote node.
To start and stop the resources under a userApplication that is controlled by the scalable controller, the controlled userApplication must be Offline.
Note
To stop the unexpected started resource, make sure to change the corresponding userApplication to the Maintenance mode, and then stop the target resource manually (if the resource is stopped without changing the mode to Maintenance mode, the resource is considered to be a resource error).
