Chapter 3. Set Up Expiration

Red Hat JBoss Data Grid uses expiration to attach one or both of the following values to an entry:

Expiration can be specified on a per-entry or per-cache basis and the per-entry configuration overrides per-cache configurations. If expiration is configured at the cache level, then the expiration defaults apply to all entries which do not explicitly specify a lifespan or max-idle value.

If expiration is not configured at the cache level, cache entries are created immortal (i.e. they will never expire) by default. Any entries that have lifespan or max-idle defined are mortal, as they will eventually be removed from the cache once one of these conditions are met.

Expired entries, unlike evicted entries, are removed globally, which removes them from memory, cache stores and the cluster.

Expiration automates the removal of entries that have not been used for a specified period of time from the memory. Expiration and eviction are different because: