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

Darrel Schneider commented on GEODE-4933:
-----------------------------------------

this ticket fixed a limitation of GEODE-3764

> Entry Expiration on Replicate region does not function correctly for Normal 
> or Preloaded regions
> ------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-4933
>                 URL: https://issues.apache.org/jira/browse/GEODE-4933
>             Project: Geode
>          Issue Type: Bug
>          Components: expiration, regions
>            Reporter: Nick Reich
>            Assignee: Nick Reich
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.6.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> When eviction with local destroy action (which causes the data policy to be 
> "preloaded") or a caching proxy ("normal" data policy) is involved in get 
> actions, last access time-based expiration does not take into account those 
> members. Members of these types are not included in the list of members to 
> query about last access time for the possibly expiring event and this results 
> in incorrect behavior: expiration of the recently accessed entry. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to