Hi, When you use the write-through mode (setWriteBehindEnabled=false) the all the puts are propagated without any delay meaning that IgniteCache.put will eventually call CacheStore.put, IgniteCache.remove->CacheStore.remove.
In the write-behind mode the data is not written right away and always propagated in batches some time later. Do you observe any performance degradation? What is your problem? Probably you need to tune the write-behind mode. — Denis > On Jul 1, 2016, at 5:02 AM, deleerhai <[email protected]> wrote: > > Hi, > > If you want to enable IgniteCache asynchronous function > (setWriteBehindEnabled (true)), and let IgniteCache in > call'put','putAll','remove','removeAll' trigger CacheStore corresponding > "add",'addAll','delete','deleteAll'. This scene to real now? > The proposed IgniteCache increases the'update'method, while'update' also > increases the CacheStore method. > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/IgniteCache-remove-cache-data-repeated-calls-to-the-deleteAll-CacheStore-method-many-times-which-is--tp6004p6031.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com.
