ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitriy Pavlov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-5874) Store TTL expire times in B+ tree on per-partition basis
Date Tue, 21 Nov 2017 17:49:01 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-5874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16261148#comment-16261148

Dmitriy Pavlov commented on IGNITE-5874:

We also need to add compatibility test for TTL caches into Ignite Compatibility suite.

Probably we should also create automatic migration or migration tool for cache page store
with TTL enabled.

See related discussion in http://apache-ignite-developers.2346864.n4.nabble.com/Data-eviction-expiration-from-Ignite-persistence-td24419.html

> Store TTL expire times in B+ tree on per-partition basis
> --------------------------------------------------------
>                 Key: IGNITE-5874
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5874
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache, persistence
>    Affects Versions: 2.1
>            Reporter: Ivan Rakov
>         Attachments: IgnitePdsWithTtlTest.java
> TTL expire times for entries are stored in PendingEntriesTree, which is singleton for
cache. When expiration occurs, all system threads iterate through the tree in order to remove
expired entries. Iterating through single tree causes contention and perfomance loss. 
> Related performance issue: https://issues.apache.org/jira/browse/IGNITE-5793
> We should keep instance of PendingEntriesTree for each partition, like we do for CacheDataTree.

This message was sent by Atlassian JIRA

View raw message