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-2089) entry-idle-time setting on the client side cache is not working as expected
Date Thu, 10 Nov 2016 22:46:58 GMT

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

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

Commit e584c4e658a082155613323748f4d849bc531bdb in incubator-geode's branch refs/heads/develop
from [~bschuchardt]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=e584c4e ]

GEODE-2089 entry-idle-time on client side cache is not working as expected

When we pull an entry in from another cache in LocalRegion.findObjectInSystem()
we end up invoking updateStatsForPut and then updateStatsForGet.  The former
method installs a lastModifiedTime from the version tag that came from the
other cache and this is used in updateStatsForPut to schedule an expiry-task
for the entry.  Then updateStatsForGet is invoked to set the lastAccessed
time of the entry to the current time.  However, by the time this is done
the entry may have already been removed by the expiry-task if the
lastModified time was too far in the past.

The fix is to establish both the lastModified and lastAccessed times in
updateStatsForPut.

I've included two of the "leaf" RegionEntry classes in the diff but all of
them had to be modified in the same way.


>  entry-idle-time setting on the client side cache is not working as expected
> ----------------------------------------------------------------------------
>
>                 Key: GEODE-2089
>                 URL: https://issues.apache.org/jira/browse/GEODE-2089
>             Project: Geode
>          Issue Type: Bug
>          Components: client/server
>            Reporter: Bruce Schuchardt
>            Assignee: Bruce Schuchardt
>
> I wrote a unit test that sets an entry-idle-time timeout on a client cache with action
local-destroy.  When the client cache pulls an old entry from the server the cache appears
to ignore the entry-idle-time and expires the entry immediately after it is put in the cache.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message