This content has been marked as final. Show 2 replies
Hi,1 person found this helpful
actually your database should not hang. Because when it hangs on one node this error will impact all the other instances as well, since this node has database blocks in memory it exclusively accesses, and when these cannot be transferred, your other nodes will "wait". Hence it is crucially important that when your disk controller hangs, the database instance gets aborted, if not even the node should get evicted.
So if your described szenario really is the case, then the service definition will not help you fix the issue. You should instead have a look at the reason, why the node does not react (or does not get an error).
If the clusternode behaves correctly then the service will failover. Just make sure you configure your clients correctly to react to this: