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

Posted to issues@geode.apache.org by "Fred Krone (JIRA)" <ji...@apache.org> on 2017/12/04 23:48:00 UTC

[jira] [Updated] (GEODE-3764) idle expiration will happen even if the entry has been accessed on a replicate

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

Fred Krone updated GEODE-3764:
------------------------------
    Issue Type: Improvement  (was: Bug)

> idle expiration will happen even if the entry has been accessed on a replicate
> ------------------------------------------------------------------------------
>
>                 Key: GEODE-3764
>                 URL: https://issues.apache.org/jira/browse/GEODE-3764
>             Project: Geode
>          Issue Type: Improvement
>          Components: docs, expiration
>            Reporter: Darrel Schneider
>            Assignee: Darrel Schneider
>             Fix For: 1.4.0
>
>
> Because idle expiration is currently always based on if the entry has been accessed on the local node it is possible that entries will idle expire even if they were accessed recently.
> Since reads are only sent to one member, the last access time is only updated on that member. The expiration action itself is distributed so if any member was not read from recently, it will cause the entry to be expired on the entire cluster.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)