Hi, Seems that you’re using the write-behind mode. Such behavior is not reproduced in the write-through mode on my side. Is it so?
In the write-behind mode updates are propagated a bit later to the store and they are propagated in batches which leads to the usage of ‘writeAll’ rather then ‘write’. You can read more on store modes here: https://apacheignite.readme.io/docs/persistent-store#overview https://apacheignite.readme.io/docs/persistent-store#write-behind-caching <https://apacheignite.readme.io/docs/persistent-store#write-behind-caching> — Denis > On Jun 29, 2016, at 5:35 AM, deleerhai <[email protected]> wrote: > > Hi, > > When the put IgniteCache data call CacheStore persistence method appears the > phenomenon of confusion, what is the reason? How to solve? > > As shown in figure: > <http://apache-ignite-users.70518.x6.nabble.com/file/n5984/cache_put.png> > <http://apache-ignite-users.70518.x6.nabble.com/file/n5984/store_addAll.png> > When calling the put method of IgniteCache,addAll CacheStore method is > called,Theoretically should call the add method of CacheStore. > <http://apache-ignite-users.70518.x6.nabble.com/file/n5984/cache_remove.png> > <http://apache-ignite-users.70518.x6.nabble.com/file/n5984/store_deleteAll.png> > > When calling the remove method of IgniteCache,deleteAll CacheStore method is > called,Theoretically should call the delete method of CacheStore. > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Put-IgniteCache-data-call-CacheStore-persistent-method-of-confusion-tp5984.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com.
