Hi Val,
We discovered that in the test above following your suggestion the cache
gets recreated and however the part swapped to the disk has not been
cleared. The file is still there after cache.destroy() gets called. The
cache swapSize does not go to 0 either. The newly created cache allows new
va
Val, the suggested workaround did work. This tells me though that somewhere
in your copy constructor for CacheConfiguration you are using a *shallow*
copy of the statefull content.
Thanks for your help,
Alex
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Cann
org.apache.ignite.cache.CachePartialUpdateException: Failed to update keys
(retry update if possible).:
[au.com.macquarie.rmg.aggengine.service.workspace.domain.WorkspaceItemKey@aede9edc,
au.com.macquarie.rmg.aggengine.service.workspace.domain.WorkspaceItemKey@aedf92dd,
..
au.com.macquarie.rm
Our use case includes clearing the cache at the end of the day and
repopulating it with new content. With a size of the cache in 1.5M records
cache.clear() works extremely slowly and we use cache.destroy(), creating a
new cache and populating it with a new content. As this works as long as all
the
In my case the remote filters are being called and return true appropriately,
however it seems that the local listeners are not always being called. I am
trying to understand what could be going wrong, starting with ruling out a
possible misunderstanding of the framework behavior regarding events
p
Hi there.I found that for Ignite V 1.5.6 and 1.5.7 Continuous query stop
working while it worked for V1.5.3.My code follows the manual:// Create new
continuous query.ContinuousQuery query = new ContinuousQuery();
query.setInitialQuery(sql); query.setRemoteFilter(new
CacheEntryEventSerializableF
