Re: Transaction progress, affinity, locks

2018-04-09 Thread Ariel Tubaltsev
Hi Pavel Makes sense Thank you Ariel -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Transaction progress, affinity, locks

2018-04-09 Thread Pavel Vinokurov
Hi Arial, >> But there are also non-transactional reads from one of the caches. Any operation on a transaction cache executes within a transaction. If the transaction isn't declared, it is created implicitly with default concurrency and isolation modes. >> There will be only 2PC commit for trans

Transaction progress, affinity, locks

2018-04-05 Thread Ariel Tubaltsev
I have 2 different caches C1, C2 on 3 nodes N1, N2, N3. I want to configure it in the most possibly reliable way to avoid any inconsistency and data loss, so both caches are REPLICATED, TRANSACTIONAL, FULL_SYNC. Most of my operations are transactions: PESSIMISTIC, SERIALIZABLE that touch both cac