Re: Ignite 2.0 transaction timeout not holding up

2017-08-29 Thread ezhuravlev
Hi, This timeout is for the whole transaction, but when for the transaction you usually need to take locks on different nodes. So, when the transaction was succeeded in acquiring locks on one node, it sends remaining timeout o next node, to acquire locks on it. For example, when you see timeout=

Ignite 2.0 transaction timeout not holding up

2017-08-28 Thread Amit Pundir
Hi, I am using Ignite 2.0 and working with transactions with a 60 seconds timeout. In the logs I see Ignite timeout exceptions with timeout less than 60 seconds in the exception message. The transaction concurrency has been set to PESSIMISTIC and the transaction isolation level is REPEATABLE_READ