Could you please tell us what the logs would say if there was a deadlock? we rollback the txn on any exception explicitly.
We are running 1.8 in UAT environment this week. It is not a simple upgrade to production, we need to let it burn in. But in UAT we never saw this issue with 1.7 either. It already happened in production, so far 3 times. -- 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-tp10536p11064.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
