[infinispan-issues] [JBoss JIRA] (ISPN-11020) Clustered Max Idle Take 2

[Dan Berindei (Jira)]

     [ https://issues.redhat.com/browse/ISPN-11020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Berindei updated ISPN-11020:
--------------------------------
           Status: Resolved  (was: Pull Request Sent)
    Fix Version/s: 10.1.1.Final
                   9.4.18.Final
       Resolution: Done


> Clustered Max Idle Take 2
> -------------------------
>
>                 Key: ISPN-11020
>                 URL: https://issues.redhat.com/browse/ISPN-11020
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Core, Expiration
>            Reporter: Will Burns
>            Assignee: Will Burns
>            Priority: Major
>             Fix For: 10.1.1.Final, 11.0.0.Final, 9.4.18.Final
>
>
> ISPN-9003 added in clustered max idle expiration. However the approach implemented can cause entries to entries to expire prematurely when a node is lost (due to only the primary having the latest access time). This was deemed not acceptable.
> The new approach will add a new touch command that is fired on an entry access of a max idle entry. This will slow down accesses as they will essentially be light weight synchronous writes, but should guarantee data is properly expired.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)