Mailing-List: contact issues-help@geode.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geode.apache.org
Date: Tue, 17 Oct 2017 04:33:00 +0000 (UTC)
From: "Sai Boorlagadda (JIRA)" <jira@apache.org>
To: issues@geode.apache.org
Message-ID: <JIRA.13107383.1507242208000.13144.1508214780125@Atlassian.JIRA>
In-Reply-To: <JIRA.13107383.1507242208000@Atlassian.JIRA>
References: <JIRA.13107383.1507242208000@Atlassian.JIRA> <JIRA.13107383.1507242208283@jira-lw-us.apache.org>
Subject: [jira] [Commented] (GEODE-3764) idle expiration will happen even if
 the entry has been accessed on a replicate
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 17 Oct 2017 04:33:09 -0000


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

Sai Boorlagadda commented on GEODE-3764:
----------------------------------------

[~dschneider] What is the possible fix? Could you through some ideas so that I can dig though?

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