You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Andrey Gura (JIRA)" <ji...@apache.org> on 2018/04/18 12:17:00 UTC

[jira] [Updated] (IGNITE-5874) Store TTL expire times in B+ tree on per-partition basis

     [ https://issues.apache.org/jira/browse/IGNITE-5874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrey Gura updated IGNITE-5874:
--------------------------------
    Fix Version/s:     (was: 2.5)
                   2.6

> 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
>            Assignee: Andrew Mashenkov
>            Priority: Major
>             Fix For: 2.6
>
>         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
(v7.6.3#76005)