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 <[email protected] > wrote: > 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 <[email protected]> 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 might be helpful. >> >> Deadlock jmc picture >> <http://apache-ignite-users.70518.x6.nabble.com/file/t1415/ >> ignite-deadlock-1.ignite-deadlock-1> >> <http://apache-ignite-users.70518.x6.nabble.com/file/t1415/ >> ignite-deadlock-2.ignite-deadlock-2> >> <http://apache-ignite-users.70518.x6.nabble.com/file/t1415/ >> ignite-deadlock-3.png> >> >> Mail thread to see the resolution flow. >> http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-0-0- >> GridUnsafe-unmonitor-deadlock-td17619.html#a17620 >> >> Thanks. >> >> >> >> >> -- >> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >> > > > > -- > Best regards, > Andrey V. Mashenkov > -- Best regards, Andrey V. Mashenkov
