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

Posted to issues@geode.apache.org by "Anthony Baker (JIRA)" <ji...@apache.org> on 2018/04/20 00:54:00 UTC

[jira] [Commented] (GEODE-3519) servers are not locking on remove or invalidate ops initiated by clients

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

Anthony Baker commented on GEODE-3519:
--------------------------------------

[~bschuchardt] can this issue be closed?

> servers are not locking on remove or invalidate ops initiated by clients
> ------------------------------------------------------------------------
>
>                 Key: GEODE-3519
>                 URL: https://issues.apache.org/jira/browse/GEODE-3519
>             Project: Geode
>          Issue Type: Bug
>          Components: client/server
>            Reporter: Bruce Schuchardt
>            Assignee: Bruce Schuchardt
>            Priority: Major
>
> While debugging a DLockToken leak I found that a Scope.GLOBAL region in a server was recording CachePerfStats.conflatedEvents.  This should be zero in a Scope.GLOBAL region because each operation on the region is supposed to be performed while holding a distributed lock on the affected key.
> The problem stems from DistributedRegion not overriding the "basicBridge" operations that handle these events and surrounding the superclass's method with locking.
> The only operations currently performing correct locking are "put" and "replace".



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