Hi, you could to know more about deadlock detection here [1]
Mentioned ticket about optiomistic transactions. Deadlock detection for pessimistic transactions (your case) is implemented in 1.7 release. I don't think that it is your case because in case of TransactionDeadlockException transaction should be rolled back and all locks should be released. But it is possible that there is bug in this place. By the way, do you have the same issue on 1.8? [1] https://apacheignite.readme.io/docs/transactions#deadlock-detection On Mon, Mar 6, 2017 at 5:16 PM, bintisepaha <binti.sep...@tudor.com> wrote: > Andrey, Could you please tell us a little bit more about the deadlock > detection feature in 1.8? > > https://issues.apache.org/jira/browse/IGNITE-2969 > > How would we able to know that there is a deadlock? Do you think that is the > case for us now in 1.7 but we can't be sure because we have no such feature? > > 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-tp10536p11038.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com.
