Andrey and Yakov,
Thank you very much.
Lin.
It seems that in this case eviction policy does not get notified properly
and most probably its internal queue differs from what is actually in
cache. Can anyone take a look?
--Yakov
2015-12-25 7:54 GMT+03:00 Lin :
> With printing code before last assertion, we can see the
Lin,
thank you for your bug report. I created ticket
https://issues.apache.org/jira/browse/IGNITE-2307 that describes your
situation.
For atomic cache internal queue of eviction policy contains all added
elements after removeAll invocation while it is empty for transactional
cache. So atomic
With printing code before last assertion, we can see the contents remains in
the case is,
LruEvictionExample.testPutAll entry Entry [key=3, val=new3]
LruEvictionExample.testPutAll entry Entry [key=6, val=new6]
LruEvictionExample.testPutAll entry Entry [key=1, val=new1]
Hi,
I have a problem when I placed cache.removeAll with the Lru eviction policy.
Here is my test case, and it does not work at the last assert.
package org.apache.ignite.examples;
import junit.framework.TestCase;
import org.apache.ignite.Ignite;
import org.apache.ignite.IgniteCache;