[ https://issues.apache.org/jira/browse/GEODE-6195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821534#comment-16821534 ]
ASF subversion and git services commented on GEODE-6195: -------------------------------------------------------- Commit 2b2fda692868b0096b17ce55bc084b2f3f9637f2 in geode's branch refs/heads/feature/GEODE-6583 from Bruce Schuchardt [ https://gitbox.apache.org/repos/asf?p=geode.git;h=2b2fda6 ] GEODE-6195 putIfAbsent may get a returned value caused by the same operation due to retry Moving the check for a retried putIfAbsent to be under the RegionEntry lock. This allows the operation to propagate throughout the cluster and allows the client to receive a valid version tag, if concurrency checks are enabled. > putIfAbsent may get a returned value caused by the same operation due to retry > ------------------------------------------------------------------------------ > > Key: GEODE-6195 > URL: https://issues.apache.org/jira/browse/GEODE-6195 > Project: Geode > Issue Type: Bug > Components: regions > Affects Versions: 1.1.0 > Reporter: Eric Shu > Assignee: Bruce Schuchardt > Priority: Major > Labels: pull-request-available > Fix For: 1.10.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > A server which does not store the entry will try the putIfAbsent operation to > host member. Currently product treats this as a failed op even though it is > due to retried operation. If it does the operation on behalf of client (and > client never failed over to another server), this could leads to client > server data inconsistency. -- This message was sent by Atlassian JIRA (v7.6.3#76005)