ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrey Gura (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (IGNITE-730) Need to implement ACCESS-TIME-TTL and UPDATE-TIME-TTL as eviction policy
Date Thu, 30 Apr 2015 12:52:06 GMT

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

Andrey Gura resolved IGNITE-730.
--------------------------------
    Resolution: Fixed

Resolved due to IGNITE-728

> Need to implement ACCESS-TIME-TTL and UPDATE-TIME-TTL as eviction policy
> ------------------------------------------------------------------------
>
>                 Key: IGNITE-730
>                 URL: https://issues.apache.org/jira/browse/IGNITE-730
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: cache, streaming
>            Reporter: Dmitriy Setrakyan
>            Assignee: Andrey Gura
>            Priority: Blocker
>             Fix For: sprint-4
>
>
> # We should reuse our LRU policy for this.
> # Just like with CREATE-TIME-TTL policy, we should keep a collection of fix-sized buckets.
> # Each bucket can be a List of entries.
> # Each bucket should keep a timestamp of when that bucket was crated.
> # However, each entry in LRU queue should keep a reference to its bucket and index specifying
it's location within that bucket (and vice-versa).
> *Access*
> Whenever an entry is accessed or updated within some bucket, it should be removed from
that bucket and added to the first bucket.
> *Eviction*
> Whenever (currentTime - bucketCreateTime) > TTL, all the entries in the bucket get
evicted. 
> We should also add a flag in {{EvictableEntry}} specifying whether the access was read
or update, e.g. {{EvictableEntry.isUpdate()}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message