Hi Val, Killing the node that acquired the lock did not release it automatically and leads whole cluster in hung state, any operation on any cache (not related to lock) are in wait state. Cluster is not able to recover seamlessly. Looks like a bug to me.
I understand lock timeout can be error-prone, if configured correctly then lock timeout can provide a second way of auto recovery in such failover cases. Is there any way to configure timeouts on lock? Explicit lock is one of the usecase we have, but Cluster auto recovery during any change to cluster is the most important, so if these 2 not going together then its a show stopper. -Sam -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cluster-hung-after-a-node-killed-tp8965p9309.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
