Hi, Incorrect implementation of CacheStore is the most probable reason, because stored entry is locked. You need to avoid lock one entry in othe.
Necessary re-write the code and re-check, I think, the issue will resolved. On Tue, Oct 25, 2016 at 1:05 AM, bintisepaha <[email protected]> wrote: > Hi, actually we use a lot of caches from cache store writeAll(). > For confirming if that is the cause of the grid stall, we would have to > completely change our design. > > Can someone confirm that this is the cause for grid to stall? referencing > cache.get from a cache store and then killing or bringing up nodes leads to > a stall? > > We see a node blocked on flusher thread while doing a cache.get() when the > grid is stalled, if we kill that node, the grid starts functioning. But we > would like to understand are we using write behind incorrectly or there are > some settings that we can use to re-balance or write-behind that might save > us from something like this. > > Thanks, > Binti > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Killing-a-node-under-load-stalls-the- > grid-with-ignite-1-7-tp8130p8449.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Vladislav Pyatkov
