Hi, >From your errors list I see many connection errors. Why does it happen?
> how ignite treats cluster topology when transaction are running on server > nodes When Ignite executes some operation in transaction it maps all involved keys to affinity nodes and then transaction will be propagated to this nodes. If transaction isn't finished and some of involved nodes left topology then transaction will be failed and rolled back. Client nodes doesn't affect transactions when join or leave cluster except of cases when client node is transaction initiator or have local cache that participates in transaction. On Tue, Mar 21, 2017 at 11:40 PM, bintisepaha <[email protected]> wrote: > Sorry for keep following up on this, but this is becoming a major issue for > us and we need to understand how ignite treats cluster topology when > transaction are running on server nodes. How do clients joining and leaving > the cluster affects txns? > > 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-tp10536p11346.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com.
