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 2017/07/11 13:57:00 UTC

[jira] [Commented] (IGNITE-5722) Cache entries stay in onheap after scan query execution for OFFHEAP_TIRED cache with expiry policy

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

Andrey Gura commented on IGNITE-5722:
-------------------------------------

Fixed https://github.com/apache/ignite/pull/2281
Waiting for TC.

> Cache entries stay in onheap after scan query execution for OFFHEAP_TIRED cache with expiry policy
> --------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-5722
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5722
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 1.0
>            Reporter: Andrey Gura
>            Assignee: Andrey Gura
>             Fix For: 2.2
>
>
> Cache entries stay in onheap after scan query execution for OFFHEAP_TIRED cache with expiry policy.
> In PeekValueExpiryAwareIterator.value() method the entry should be touched after unswap.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)