Re: Deadlock detected while accessing caches

Hi Amit, Transactions on unsorted keysets also can cause a deadlock. However, unlikely to getAll on Atimoc cache, Ignite should detect deadlock in transactions. On Thu, Nov 9, 2017 at 3:31 PM, Andrey Mashenkov wrote: > Hi dark, > > It is known issue. The only workaround here is to presort keys

Re: Deadlock detected while accessing caches

Hi dark, It is known issue. The only workaround here is to presort keys before getAll \ putAll. On Fri, Nov 3, 2017 at 10:05 PM, dark wrote: > I also experienced a deadlock while attempting putAll using a HashMap. > I used AtomicityMode as ATOMIC. > If you are like me, the following process mig

Re: Deadlock detected while accessing caches

I also experienced a deadlock while attempting putAll using a HashMap. I used AtomicityMode as ATOMIC. If you are like me, the following process might be helpful. Deadlock jmc picture

Re: Deadlock detected while accessing caches

Thanks Andrew for the response. I don't have any getAll/putAll operations but have discovered transaction operations on unsorted keysets on a cache which can cause a deadlock. The deadlock detected message though shows two different caches whereas the unsorted keys are accessed on a single cache o

Re: Deadlock detected while accessing caches

I also experienced a deadlock while attempting putAll using a HashMap. I used AtomicityMode as ATOMIC. If you are like me, the following process might be helpful. Deadlock jmc picture

Re: Deadlock detected while accessing caches

Hi Amit, Do you use getAll, putAll or invokeAll on non-sorted keysets? On Thu, Nov 2, 2017 at 9:43 PM, Amit Pundir wrote: > Hi, > I have a Ignite 2.0 cluster of 8 servers and 8 clients. It has 6 caches > which are transactional and partitioned. > I use pessimistic transactions with a timeout o

Deadlock detected while accessing caches

Hi, I have a Ignite 2.0 cluster of 8 servers and 8 clients. It has 6 caches which are transactional and partitioned. I use pessimistic transactions with a timeout of 60 seconds. Under performance testing, I found a deadlock message in the log. I have reviewed the code and there is no cyclic access