geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-3764) idle expiration will happen even if the entry has been accessed on a replicate
Date Wed, 27 Dec 2017 22:45:00 GMT

    [ https://issues.apache.org/jira/browse/GEODE-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16304842#comment-16304842
] 

ASF GitHub Bot commented on GEODE-3764:
---------------------------------------

davebarnes97 opened a new pull request #1207: GEODE-3764 idle expiration will happen even
if the entry has been acc…
URL: https://github.com/apache/geode/pull/1207
 
 
   …essed on a replicate
   
   NOTE: I intentionally omitted the `geode.restoreIdleExpirationBehavior` system property
from the user guide, but plan to document it in the release note describing this fix. 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> 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)

Mime
View raw message