Hello Dave, The off-heap memory became the only memory mode supported in 2.0: https://apacheignite.readme.io/docs/page-memory <https://apacheignite.readme.io/docs/page-memory>
There is an option to enable caching of key-value entries in Java heap if needed: https://apacheignite.readme.io/docs/page-memory#on-heap-caching <https://apacheignite.readme.io/docs/page-memory#on-heap-caching> If the heap caching is enabled then these eviction mechanism can be used (the data is evicted from the Java heap only): https://apacheignite.readme.io/docs/evictions#on-heap-cache-entries-based-eviction <https://apacheignite.readme.io/docs/evictions#on-heap-cache-entries-based-eviction> To evict data from the off-heap page memory you need to use page-based eviction: https://apacheignite.readme.io/v2.0/docs/evictions#section-page-based-eviction <https://apacheignite.readme.io/v2.0/docs/evictions#section-page-based-eviction> — Denis > On May 23, 2017, at 5:01 PM, Dave Marion <[email protected]> wrote: > > If you have off-heap memory configured and then create a cache with on-heap > enabled and an eviction policy, does the on-heap eviction place the evicted > K/V into off-heap memory? I'm new to Ignite and I'm looking for a local-only > tiered cache solution (on-heap and off-heap memory usage). The 2.0 > documentation does not definitively state that it does this. Is there an > example for configuring such a cache? Thanks for the help. > > - Dave >
