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

Posted to issues@ignite.apache.org by "Andrew Mashenkov (JIRA)" <ji...@apache.org> on 2016/09/29 13:48:20 UTC

[jira] [Updated] (IGNITE-3948) TTL manager continues to track evicted entries

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

Andrew Mashenkov updated IGNITE-3948:
-------------------------------------
    Assignee: Andrey Gura  (was: Andrew Mashenkov)

> TTL manager continues to track evicted entries
> ----------------------------------------------
>
>                 Key: IGNITE-3948
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3948
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 1.7
>            Reporter: Andrey Gura
>            Assignee: Andrey Gura
>             Fix For: 1.8
>
>
> Cache uses only heap memory and has eviction and expiry policies. During loading data into cache TTL manager consumes heap memory even if entries were evicted because it still track this entries. 
> It's ok in case of offheap memory or/and swap are enabled but doesn't make sense in case of using only heap memory.
> See also http://stackoverflow.com/questions/39447690/apache-ignite-cache-eviction-still-in-memory



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