Yes, you are right.
On Wed, Jun 20, 2018 at 4:13 PM the_palakkaran wrote:
> So to conclude, if I have enabled on heap storage for cache(using
> cache.setOnHeapEnabled(true),
> then :
> 1. Still data will be stored off heap, but will be loaded to heap. To
> escape
> out of memory error, I have to
So to conclude, if I have enabled on heap storage for cache(using
cache.setOnHeapEnabled(true),
then :
1. Still data will be stored off heap, but will be loaded to heap. To escape
out of memory error, I have to set eviction policies.
2. Off heap entries will be written to disk based on data page ev
DataRegionConfiguration.setMaxSize() should be used to limit offheap memory
usage.
On Tue, Jun 19, 2018 at 2:35 PM the_palakkaran wrote:
> So how do I limit cache size if ignite native persistence is enabled using
> dataRegionCfg.setPersistenceEnabled(true)? I don't want it to keep a lot of
> da
So how do I limit cache size if ignite native persistence is enabled using
dataRegionCfg.setPersistenceEnabled(true)? I don't want it to keep a lot of
data in memory and others may be kept on disk. That is the requirement.
Also, I do have on heap cache enabled. But I read in many threads that
Igni
Hi,
DataPageEvictionMode is about algorithm of choosing page to be replaced.
EvictionPolicy is what you are looking for. E.g. FifoEvictionPolicy or
LruEvictionPolicy.
It looks like EvictionPolicies can't be used with persistence as all of
them uses non-persistent structures to track cache entries
Hi,
DataPageEvictionMode is deprecated now, right? What should I do to evict my
off heap entries? Also, can I limit off heap memory usage?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi John,
1. Actually it is. By default data page eviction is disabled
(DataPageEvictionMode.DISABLED) and when no memory left, it will throw
IgniteOutOfMemoryException.
2. If you have enabled persistence - no data will be lost, dirty pages
will be written do disk. In other words Ignite starts
I appreciate the nice explanation. I got a few more questions:
1. For the case where on-heap caching and persistent are both disabled,
why does Ignite throw out out-dated pages from off-heap? Why not throw OOM
error since the out-dated pages are not backed by persistent store and
thro
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, the
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
Hi,
I have been reading through Ignite doc and I still have these questions. I
appreciate your answer.
Assume my Ignite native persistence is *not *enabled:
1. if on-heap cache is also not enabled, then there are no entry-based
evictions, right?
2. if on-heap cache is now enabled, does
11 matches
Mail list logo
