[jira] [Commented] (GEODE-6108) client putIfAbsent operation may get a returned value caused by the same operation due to retry

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

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

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

Commit eb57bfd45e51dd3ac150594e9aa4763764d8bd2c in geode's branch refs/heads/feature/GEODE-6108 from eshu
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=eb57bfd ]

GEODE-6108: Handle client putIfAbsent returns value due to retry

 * Check putIfAbsent return value from server if it could caused by retry.
 * Make sure client putIfAbsent operation message.isRetry is set if it retries after failed when using singleHop


> client putIfAbsent operation may get a returned value caused by the same operation due to retry
> -----------------------------------------------------------------------------------------------
>
>                 Key: GEODE-6108
>                 URL: https://issues.apache.org/jira/browse/GEODE-6108
>             Project: Geode
>          Issue Type: Bug
>          Components: client/server
>            Reporter: Eric Shu
>            Assignee: Eric Shu
>            Priority: Major
>
> A client putIfAbsent operation succeeds on the server. However, before server send back message to client, the server is lost. Client will retry the operation to another server. In some corner case, the value (caused by the same client operation) will be returned to the client. This will prevent the originator to apply the same putIfAbsent operation on the client and leads to data inconsistency. 



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