Hi, Assume you have disabled onheapCahe and disabled persistence. In that case you may configure only datapage eviction mode, then outdated pages will be thrown away, when no free memory will be available for Ignite. Also you cannot configure per-entry eviction.
OK, if you enable onheapCache, then Ignite will store on heap every entry that was read from off-heap (or disk). Next reads of it will not require off-heap readings, and every update will write to off-heap. To limit size of onheapCache you may set CacheConfiguration.setEvictionPolicy(), but it will not evict off-heap entries. So, off-heap eviction may be controlled with DataPageEvictionMode only, and as you suggested, it clears entries one-by-one from page, checking for current locks (transaction locks as well). If entry is locked, it won't be evicted. Thanks! -Dmitry. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
