Hello Team, Looks like I am faced to similar issue in case of cache rebalancing. I.e. there are few nodes and cache data are being modified/updated via EntryProcessor. And at some moment additional node is joined to grid. And finally (after rebalance complete and update complete) I got cache values that are less than expected for some cache entries(but values are aligned to how they were combined into single update batch). This time I am not getting assertion error but after enabling debug and etc. I am getting messages like:
... cache.GridCacheMapEntry] - Received entry update with smaller version than current (will ignore) ... So, I am wondering is it related to versioning issue described previously in this thread or is it another (known?) issue or perhaps it is not an issue at all and I am doing/expecting something wrong? Thanks, 2016-02-13 9:17 GMT+02:00 Myron Chelyada <[email protected]>: > Will try to apply some workaround and looking forward to fix. > > 2016-02-12 16:58 GMT+02:00 Alexey Goncharuk <[email protected]>: > >> Myron, >> >> Thank you for reporting the issue. The assertion happens when the value >> is present in the store, absent in the cache and you run invokeAll(). As a >> temporary solution, you can either call invoke() for each particular key >> individually, or call getAll() for the keys prior to calling invokeAll() >> (this will pre-load the values to the cache). >> Since the issue is pretty critical, I believe it will be fixed in 1.6 (if >> not earlier). >> >> Yakov, Sam, >> I created a ticket [1] and suggested a fix there, can you take a look and >> check if the fix is ok? >> >> Thanks, >> AG >> >> [1] https://issues.apache.org/jira/browse/IGNITE-2645 >> > >
