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

Posted to issues@ignite.apache.org by "Dmitriy Setrakyan (JIRA)" <ji...@apache.org> on 2018/04/01 14:46:00 UTC

[jira] [Assigned] (IGNITE-8027) Expired entry appears back in case of node restart with persistence enabled

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

Dmitriy Setrakyan reassigned IGNITE-8027:
-----------------------------------------

    Assignee: Vladimir Ozerov

> Expired entry appears back in case of node restart with persistence enabled
> ---------------------------------------------------------------------------
>
>                 Key: IGNITE-8027
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8027
>             Project: Ignite
>          Issue Type: Bug
>          Components: persistence
>    Affects Versions: 2.4
>            Reporter: Valentin Kulichenko
>            Assignee: Vladimir Ozerov
>            Priority: Major
>             Fix For: 2.5
>
>
> Detailed description of the issue and a reproducer can be found in this thread: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Expiry-Inconsistency-with-Native-Persistence-td20390.html
> In short, if entry expires, it can then be read again after node restart. This is reproduced ONLY if node is killed with 'kill -9', in case of graceful stop everything works fine.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)