I'm not quite sure this is relevant to your issue. I've experienced the hanging issue on ignite 1.8.0 when topology changed. https://issues.apache.org/jira/browse/IGNITE-4450 might get to fix the problem. FYR.
2017-03-16 1:03 GMT+08:00 bintisepaha <binti.sep...@tudor.com>: > Andrey, do you think topology changes with client nodes (not server nodes) > leaving and joining the cluster may have any impact on transaction? > > twice out of the 4 times we saw topology changes while the last successful > update was done to the key that was eventually locked. > > Yesterday we saw this same issue on another cache. We are due for 1.8 > upgrade soon, but given that no one else has seen this issue before, we are > not sure if 1.8 would have fixed it either. > > Let us know what you think. > > 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-tp10536p11203.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
