Re: [2.8.1]Checking optimistic transaction state on remote nodes

2020-11-23 Thread Ilya Kasnacheev
Hello! You can set concurrency mode and isolation for transactions by default by specifying them in TransactionConfiguration. Otherwise you are correct. Regards, -- Ilya Kasnacheev пн, 23 нояб. 2020 г. в 14:49, 38797715 <38797...@qq.com>: > Hi Ilya, > > Then confirm again that according to

Re: [2.8.1]Checking optimistic transaction state on remote nodes

2020-11-23 Thread 38797715
Hi Ilya, Then confirm again that according to the log message, optimistic transaction and READ_COMMITTED are used for single data operation of transactional cache? If transactions are explicitly turned on, the default concurrency model and isolation level are pessimistic and

Re: [2.8.1]Checking optimistic transaction state on remote nodes

2020-11-20 Thread Ilya Kasnacheev
Hello! It will happen when the node has left but the transaction has to be committed. Most operations on transactional cache will involve implicit transactions so there you go. Regards, -- Ilya Kasnacheev чт, 19 нояб. 2020 г. в 16:46, 38797715 <38797...@qq.com>: > Hi community, > > Although

[2.8.1]Checking optimistic transaction state on remote nodes

2020-11-19 Thread 38797715
Hi community, Although there is a transactional cache, no transaction operation is performed, but there is a lot of output below in the log. Why? [2020-11-16 14:01:44,947][INFO ][sys-stripe-8-#9][IgniteTxManager] Checking optimistic transaction state on remote nodes [tx=GridDhtTxLocal