Infinispan Expiration: Difference between revisions
| Line 18: | Line 18: | ||
=Configuration= | =Configuration= | ||
For more details about expiration, see: | 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: | ||
<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;"> | <blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;"> | ||
:[[Infinispan_Cache_Container_Configuration#.3Cexpiration.3E|Expiration Configuration]] | :[[Infinispan_Cache_Container_Configuration#.3Cexpiration.3E|Expiration Configuration]] | ||
</blockquote> | </blockquote> | ||
Revision as of 02:30, 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.
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: