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 2022/03/18 00:31:00 UTC

[jira] [Commented] (GEODE-10130) cq destroy event in replicate region can be missing

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

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

Commit e08bba5d79f34b7d80c09b0878f8f0ee23f9cfc7 in geode's branch refs/heads/develop from Eric Shu
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=e08bba5 ]

GEODE-10130: Check containsKey under synchronization. (#7452)

* containsKey in HashMap can return false even though the key exists in
   the map possibly due to map resizes as other concurrent operations
   occur. Now it will be checked under synchronized lock.

> cq destroy event in replicate region can be missing 
> ----------------------------------------------------
>
>                 Key: GEODE-10130
>                 URL: https://issues.apache.org/jira/browse/GEODE-10130
>             Project: Geode
>          Issue Type: Bug
>          Components: cq
>    Affects Versions: 1.12.0, 1.13.0, 1.14.4, 1.15.0
>            Reporter: Eric Shu
>            Assignee: Eric Shu
>            Priority: Major
>              Labels: GeodeOperationAPI, pull-request-available
>
> In geode, cq event for replicated region are cached so that when destroy event comes in, we can just use cached value to determine if a client need the cq event (instead of evaluate the query again for performance). 
> However, there is a synchronization issue in ServerCQResultsCacheReplicateRegionImpl that could cause geode failed to find the cached event.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)