ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Evgenii Zhuravlev <e.zhuravlev...@gmail.com>
Subject Re: deadlock
Date Tue, 31 Oct 2017 10:11:15 GMT
Hi,

Most possible you update entries in different order. Before using bulk
operations such as updateAll removeAll invokeAll, make sure that entries
you applying to it sorted in the same order

Evgenii

2017-10-31 9:51 GMT+03:00 shawn.du <shawn.du@neulion.com.cn>:

> Hi,
>
> My ignite server stop to response.  Any client can't connect it, and I
> found dead lock in logs,
> what's the possible reason for this?  I use ignite 1.9.0.
>
> Thanks in advance.
> ================log===================================
> deadlock: true
> completed: 29519967
> Thread [name="sys-stripe-12-#13%null%", id=36, state=BLOCKED,
> blockCnt=308, waitCnt=28469776]
>     Lock [object=o.a.i.i.processors.cache.distributed.dht.atomic.
> GridDhtAtomicCacheEntry@4f5b4fce, ownerName=sys-stripe-9-#10%null%,
> ownerId=33]
>         at sun.misc.Unsafe.monitorEnter(Native Method)
>         at o.a.i.i.util.GridUnsafe.monitorEnter(GridUnsafe.java:1136)
>         at o.a.i.i.processors.cache.distributed.dht.atomic.
> GridDhtAtomicCache.lockEntries(GridDhtAtomicCache.java:2958)
>         at o.a.i.i.processors.cache.distributed.dht.atomic.
> GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1793)
>         at o.a.i.i.processors.cache.distributed.dht.atomic.
> GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1721)
>         at
>
> Thanks
> Shawn
>
>

Mime
View raw message