There are no something suspicious in stack trace. You can check that key is locked using IgniteCache.isLocalLocked() method. For remote nodes you can run task that performs this checking.
Could you please provide full logs for analysis? On Tue, Feb 21, 2017 at 6:48 PM, bintisepaha <binti.sep...@tudor.com> wrote: > Andrey, thanks for getting back. > I am attaching the stack trace. Don't think the cause is a deadloc, but the > trace is long so maybe I am missing out something, let me know if you find > something useful. > > We cannot ourselves reproduce this issue as there are no errors on the prior > successful update. It feels like the txn was marked successful, but on one > of the keys the lock was not released. and later when we try to access the > key, its locked, hence the exceptions. > > No messages in the logs for long running txns or futures. > By killing the node that holds the key, the lock is not released. > > Is there a way to query ignite to see if the locks are being held on a > particular key? Any code we can run to salvage such locks? > > Any other suggestions? > > Thanks, > Binti > > > > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Pessimistic-TXN-did-not-release-lock-on-a-key-all-subsequent-txns-failed-tp10536p10764.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com.
