ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Denis Magda <dma...@gridgain.com>
Subject Re: transaction not timing out
Date Tue, 28 Jun 2016 06:36:52 GMT
Hi Binti,

In case of writeAll the locks for keys are acquired sequentially. To avoid deadlocks you need
to use an ordered data structure like TreeSet the will hold the keys.

Alex G. can you join the thread and provide your thoughts on why the timeout is not honored
for the discussed transactional mode.


> On Jun 28, 2016, at 1:14 AM, bintisepaha <binti.sepaha@tudor.com> wrote:
> Denis, We will reproduce with pessismistic/repeatable read next week and
> update you.
> How is writeAll handled by the framework - in a txn? 
> Was someone able to look at the timeout not being honored while committing?
> What would cause this issue? 
> --
> View this message in context: http://apache-ignite-users.70518.x6.nabble.com/transaction-not-timing-out-tp5540p5934.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message