Hi, Your thread is waiting for partition exchange that possibly hangs due to some reason.
Is it possible, to share logs and thread dumps at a time when you observed hanging? On Sun, Oct 29, 2017 at 4:09 AM, naresh.goty <[email protected]> wrote: > Hi, > > We are seeing threads blocked when reading (only reads not writes) for data > from cache using Ignite.affinitiyCall(). > > Scenario: > 1) Two nodes are started in a cluster. Perform cache reads using > Ignite.affinityCall() and it works. > 2) One node is stopped, and perform cache read again using > Ignite.affinityCall() and it is blocked. > > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > at java.util.concurrent.locks.LockSupport.park(LockSupport. > java:304) > at > org.apache.ignite.internal.util.future.GridFutureAdapter. > get0(GridFutureAdapter.java:176) > at > org.apache.ignite.internal.util.future.GridFutureAdapter. > get(GridFutureAdapter.java:139) > at > org.apache.ignite.internal.processors.affinity. > GridAffinityAssignmentCache.awaitTopologyVersion( > GridAffinityAssignmentCache.java:557) > at > org.apache.ignite.internal.processors.affinity. > GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache. > java:468) > at > org.apache.ignite.internal.processors.cache.GridCacheAffinityManager. > assignment(GridCacheAffinityManager.java:238) > at > org.apache.ignite.internal.processors.affinity.GridAffinityProcessor. > affinityCache(GridAffinityProcessor.java:375) > at > org.apache.ignite.internal.processors.affinity.GridAffinityProcessor. > affinityKey(GridAffinityProcessor.java:306) > at > org.apache.ignite.internal.IgniteComputeImpl.affinityCallAsync0( > IgniteComputeImpl.java:333) > at > org.apache.ignite.internal.IgniteComputeImpl.affinityCall( > IgniteComputeImpl.java:301) > > > Thanks, > Naresh > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > -- Best regards, Andrey V. Mashenkov
