Hi Sam, If there is an explicit lock that you acquired and not released properly, there is not much we can do. Explicit locks must be released explicitly, doing this by timeout even more error-prone in my view. BTW, only stopping the node that acquired the lock should've helped as well, because locks are released in this case automatically.
-Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cluster-hung-after-a-node-killed-tp8965p9247.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
