[JBoss JIRA] (ISPN-11020) Clustered Max Idle Take 2
by Will Burns (Jira)
[ https://issues.redhat.com/browse/ISPN-11020?page=com.atlassian.jira.plugi... ]
Will Burns updated ISPN-11020:
------------------------------
Fix Version/s: 11.0.0.Final
> 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: 11.0.0.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)
4 years, 11 months
[JBoss JIRA] (ISPN-11020) Clustered Max Idle Take 2
by Will Burns (Jira)
[ https://issues.redhat.com/browse/ISPN-11020?page=com.atlassian.jira.plugi... ]
Will Burns updated ISPN-11020:
------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/infinispan/infinispan/pull/7722
> 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: 11.0.0.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)
4 years, 11 months