Infinispan Expiration: Difference between revisions
| Line 10: | Line 10: | ||
=Overview= | =Overview= | ||
Expiration is the cache feature that allows the user to configure a ''lifespan'' and/or ''maximum idle time'' to cache entries. The entires that exceed these times are treated as invalid and are removed from the cache. | Expiration is the cache feature that allows the user to configure a ''[[#Lifespan|lifespan]]'' and/or ''[[#Maximum_Idle_Time|maximum idle time]]'' to cache entries. The entires that exceed these times are treated as invalid and are removed from the cache. | ||
When an entry is removed from the cache due to expiration, it is NOT [[Infinispan_Concepts#Passivation|passivated]] (like [[Infinispan Eviction|evicted]] entries when passivation is turned on) but simply discarded. Also unlike eviction, expired entries are removed globally - from memory, cache stores, and cluster-wide. | When an entry is removed from the cache due to expiration, it is NOT [[Infinispan_Concepts#Passivation|passivated]] (like [[Infinispan Eviction|evicted]] entries when passivation is turned on) but simply discarded. Also unlike eviction, expired entries are removed globally - from memory, cache stores, and cluster-wide. | ||
If expiration is not explicitly configured or programmed via the API, the entires are by default ''immortal'' and do not have a lifespan or a maximum idle time. | If expiration is not explicitly configured or programmed via the API, the entires are by default ''immortal'' and do not have a lifespan or a maximum idle time. | ||
=Lifespan= | |||
=Maximum Idle Time= | |||
=Configuration= | =Configuration= | ||
Revision as of 02:31, 21 October 2016
External
Internal
Overview
Expiration is the cache feature that allows the user to configure a lifespan and/or maximum idle time to cache entries. The entires that exceed these times are treated as invalid and are removed from the cache.
When an entry is removed from the cache due to expiration, it is NOT passivated (like evicted entries when passivation is turned on) but simply discarded. Also unlike eviction, expired entries are removed globally - from memory, cache stores, and cluster-wide.
If expiration is not explicitly configured or programmed via the API, the entires are by default immortal and do not have a lifespan or a maximum idle time.
Lifespan
Maximum Idle Time
Configuration
Lifespans and/or maximum idle times can be configured by adding the <expiration/> element to the cache configuration sections. For more details about expiration configuration, see: