Infinispan Expiration: Difference between revisions
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
=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. 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. | |||
Unlike eviction, expired entries are removed globally - from memory, cache stores, and cluster-wide. | |||
By default entries created are immortal and do not have a lifespan or maximum idle time. Using the cache API, mortal entries can be created with lifespans and/or maximum idle times. Further, default lifespans and/or maximum idle times can be configured by adding the <expiration /> element to your <*-cache /> configuration sections. | |||
=Configuration= | =Configuration= | ||
Revision as of 02:25, 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.
Unlike eviction, expired entries are removed globally - from memory, cache stores, and cluster-wide. By default entries created are immortal and do not have a lifespan or maximum idle time. Using the cache API, mortal entries can be created with lifespans and/or maximum idle times. Further, default lifespans and/or maximum idle times can be configured by adding the <expiration /> element to your <*-cache /> configuration sections.
Configuration
For more details about expiration, see: