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

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on IGNITE-3948:
----------------------------------------

GitHub user AMashenkov opened a pull request:

    https://github.com/apache/ignite/pull/1101

    IGNITE-3948: TTL manager continues to track evicted entries

    Fixed

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-3948

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/1101.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1101
    
----
commit 4d713331c510a65c791963d2c9d722b14dd5ab17
Author: Andrey V. Mashenkov <an...@gmail.com>
Date:   2016-09-22T09:23:20Z

    Fixed

----


> 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: Andrew Mashenkov
>
> 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)