[jira] [Commented] (GEODE-10211) A retried operation does not set possible duplicate in the event if retried on an accessor

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

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

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

Commit ead41c0221ba029bec3d3ed57c5232000601d7ce in geode's branch refs/heads/develop from Eric Shu
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ead41c0221 ]

GEODE-10211: Correctly check persistence on accessor (#7546)

 * To set possible duplicate for an event, whether region is persistent
   need to be determined. Allow an accessor to check the setting through
   profiles.

* Changed the order of condition check so that no need to send the find
version tag message to peers if persistence is true.

> A retried operation does not set possible duplicate in the event if retried on an accessor
> ------------------------------------------------------------------------------------------
>
>                 Key: GEODE-10211
>                 URL: https://issues.apache.org/jira/browse/GEODE-10211
>             Project: Geode
>          Issue Type: Bug
>          Components: persistence, regions
>            Reporter: Eric Shu
>            Assignee: Eric Shu
>            Priority: Major
>              Labels: GeodeOperationAPI, blocks-1.15.0​, pull-request-available
>
> In geode, or persistent region, it is possible that all persistent copies went offline. So possible duplicate should be set in the event, even though no members has the event in the event tracker.
> Currently, the code handling this will miss the setting if the retry occurs on an accessor (localMaxMemory set to 0) case.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)