[
https://issues.apache.org/jira/browse/IGNITE-7992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470934#comment-16470934
]
Denis Magda commented on IGNITE-7992:
-------------------------------------
Updated the doc with the following information.
The expiration policies work this way depending on a memory configuration of
your deployment:
* In-Memory Mode (data is stored solely in RAM): expired entries are purged
from RAM completely.
* Memory + Ignite persistence: expired entries are removed from both memory and
disk tiers.
* Memory + 3rd party persistence: expired entries are removed from the memory
tier only (Ignite) and left untouched in the 3rd party persistence (RDBMS,
NoSQL, and other databases).
* Memory + Swap: expired entries are removed from both RAM and swap files.
> Clarify how expiration policy works for durable memory and 3rd pary
> -------------------------------------------------------------------
>
> Key: IGNITE-7992
> URL: https://issues.apache.org/jira/browse/IGNITE-7992
> Project: Ignite
> Issue Type: New Feature
> Components: documentation
> Affects Versions: 2.4
> Reporter: Denis Magda
> Assignee: Denis Magda
> Priority: Major
> Fix For: 2.5
>
>
> Update the expiration policies page with the result of the following
> discussion:
> http://apache-ignite-developers.2346864.n4.nabble.com/Data-eviction-expiration-from-Ignite-persistence-td24419i20.html#a28081
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
