[
https://issues.apache.org/jira/browse/GEODE-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210212#comment-16210212
]
Darrel Schneider commented on GEODE-3764:
-----------------------------------------
In fixing this we do not want every read to be distributed.
Something we could do is when we see that it has expired locally we could send
a message to all replicates of the region that expired.
If any of them have a more recent last access time then it should be used to
update the local entry's last access time and to reschedule the entry for
expiration.
I think this approach would fit well with our current expiration implementation
and would prevent any extra work being done by read operations.
> 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: docs, expiration
> Reporter: Darrel Schneider
> Assignee: 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)
