[
https://issues.apache.org/jira/browse/GEODE-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209680#comment-16209680
]
Sai Boorlagadda commented on GEODE-3764:
----------------------------------------
[~dschneider] I found this [PR|https://github.com/apache/geode/pull/940]
already fixes this issue. Will review this PR to understand the fix.
> 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: Bug
> Components: expiration
> Reporter: Darrel Schneider
>
> 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)
