You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "Sai Boorlagadda (JIRA)" <ji...@apache.org> on 2019/04/12 23:34:00 UTC

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

     [ https://issues.apache.org/jira/browse/GEODE-6195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sai Boorlagadda updated GEODE-6195:
-----------------------------------
    Fix Version/s:     (was: 1.9.0)

> 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
>          Time Spent: 1.5h
>  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)