[
https://issues.apache.org/jira/browse/GEODE-6195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16723310#comment-16723310
]
ASF subversion and git services commented on GEODE-6195:
--------------------------------------------------------
Commit 334db40578dc963e3868f9ec285be7e6c4571d7f in geode's branch
refs/heads/feature/GEODE-6143-5 from pivotal-eshu
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=334db40 ]
GEODE-6195: Check if returned value is caused by a retried putIfAbsent
operation (#2993)
* GEODE-6195: Check if returned value is caused by a retried putIfAbsent
operation
* Treats a retried putIfAbsent operation a successful one if returned value
is the value to be put
* Move the check value methods to ValueComparisonHelper class.
> 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: Eric Shu
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 20m
> 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)
