If the transactions are PESSIMISTIC/REPEATABLE_READ and both are executed in parallel then the chances are high that one transaction will be blocked by the other because one of them will hold a lock on the key.
In case of OPTIMISTIC/SERIALIZABLE transaction a TransactionOptimisticException may be generated for one of the transaction and you will need to re-execute it from scratch. Hope this makes things clearer for you. — Denis > On Jun 17, 2016, at 1:21 PM, amitpa <ami...@nrifintech.com> wrote: > > yes, I understand that. > > In production we plan to use that, however one question:- > > In this case if I use the same key in different transactiosn would it impact > performance or it will have no impact? > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Ignite-performance-improvements-tp5623p5710.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com.
