[jira] [Commented] (GEODE-4933) Entry Expiration on Replicate region does not function correctly for Normal or Preloaded regions

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

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

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

GEODE-4933: Include members with NORMAL and PRELOADED data policy in … (#1676)

* GEODE-4933: Include members with NORMAL and PRELOADED data policy in expiration

  * If the data policy for a replicate region is PRELOADED, for example, if
    eviction is used and local destroy is the eviction action, that member was
    being excluded from the set of members to get last access time before
    expiration. Those members are now included.

  * Members that were caching proxies, thus having the NORMAL data policy,
    were also being excluded and are not included in the last access time
    lookup.


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