[jira] [Updated] (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 ] Maxim Muzafarov updated IGNITE-8027: Fix Version/s: (was: 2.10) > 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 > > 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 (v8.3.4#803005)
[jira] [Updated] (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 ] Aleksey Plekhanov updated IGNITE-8027: -- Fix Version/s: (was: 2.9) 2.10 > 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.10 > > > 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 (v8.3.4#803005)
[jira] [Updated] (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 ] Maxim Muzafarov updated IGNITE-8027: Fix Version/s: (was: 2.8) 2.9 > 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.9 > > > 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 (v8.3.4#803005)
[jira] [Updated] (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 ] Vladimir Ozerov updated IGNITE-8027: Fix Version/s: (was: 2.7) 2.8 > 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)
[jira] [Updated] (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 ] Nikolay Izhikov updated IGNITE-8027: Fix Version/s: (was: 2.8) 2.7 > 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.7 > > > 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)
[jira] [Updated] (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 ] Vladimir Ozerov updated IGNITE-8027: Fix Version/s: (was: 2.7) 2.8 > 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.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)
[jira] [Updated] (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 Pavlov updated IGNITE-8027: --- Fix Version/s: (was: 2.6) 2.7 > 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.7 > > > 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)
[jira] [Updated] (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 ] Andrey Gura updated IGNITE-8027: Fix Version/s: (was: 2.5) 2.6 > 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.6 > > > 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)
