[
https://issues.apache.org/jira/browse/IGNITE-8027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16630001#comment-16630001
]
Vladimir Ozerov commented on IGNITE-8027:
-----------------------------------------
Moved to 2.8 due to inactivity. Please feel free to move back if you will be
able to complete the ticket by AI 2.7 code freeze date, September 30, 2018.
> 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
> Priority: Major
> Fix For: 2.8
>
>
> 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)
