Preventing OOM
Apache Ignite can be configured to persist entries (native or third-party) by enabling the persistence flag, or it may not persist data at all. When native persistence is turned on, then Ignite stores entries in memory and on disk. When native persistence is turned off (either using a third-party persistence store or no persistence), then Ignite uses the off-heap memory to store the entries and allocates new pages in RAM when required. We know that Ignite's durable memory has a maximum limit (20% of RAM or an overridden value); when that limit is reached and Ignite cannot allocate a page, it purges some of the data to prevent OOM errors. This purging technique is known as eviction, and Ignite provides APIs to configure the ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access