geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-3764) idle expiration will happen even if the entry has been accessed on a replicate
Date Mon, 23 Oct 2017 23:27:01 GMT

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

ASF subversion and git services commented on GEODE-3764:
--------------------------------------------------------

Commit 0259f7765a7043813f0a786a7fd5d01e422d2408 in geode's branch refs/heads/develop from
[~dschneider]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=0259f77 ]

GEODE-3764: prevent early idle expiration (#940)

Idle expiration now sends a message to others checking
if they have been read more recently. If so and if given
the new last access time the entry is not expired then
the expiration is rescheduled.
This is only done for distributed expiration actions.
This change applies to both replicates and partitioned regions.

The system property "geode.restoreIdleExpirationBehavior" can
be set to true to restore the previous idle expiration behavior.

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

Mime
View raw message