ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Setrakyan <dsetrak...@apache.org>
Subject Re: Data eviction/expiration from Ignite persistence
Date Thu, 15 Mar 2018 02:01:13 GMT
On Wed, Mar 14, 2018 at 1:41 PM, Alexey Goncharuk <
alexey.goncharuk@gmail.com> wrote:

> Denis,
> With the approach of Ignite Durable Memory there is no difference between
> 'memory' and 'disk'. The data is expired from the Ignite data storage which
> can be persisted or not. Before persistence was introduced, TTL was mostly
> used when write-through was enabled, otherwise data was cleared from Ignite
> data storage. Currently, the situation stays the same - if an entry is
> expired, it is removed from the Ignite storage, which looks absolutely
> consistent to me.

Agree with AG. There is a difference between expiration and eviction. If an
entry is expired, then it should be removed from the store, regardless if
it is in memory or on disk.

However, evicting from memory because there is not enough space does not
remove an entry from the store.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message