You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/04/12 20:22:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16816618#comment-16816618 ] 

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

Commit 9f85d83e031ad8a46267c014baea53bd8970bea0 in geode's branch refs/heads/feature/GEODE-6195b from Bruce Schuchardt
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=9f85d83 ]

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.

This also fixes GEODE-6630, "RedundancyLogger might throw NPE" because
tests were frequently running into that issue.


> 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.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)