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

2022-03-17 Thread Eric Shu (Jira)


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

Eric Shu updated GEODE-10130:
-
Affects Version/s: 1.14.0
   (was: 1.15.0)
   (was: 1.14.4)

> 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.0
>Reporter: Eric Shu
>Assignee: Eric Shu
>Priority: Major
>  Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.15.0
>
>
> 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)


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

2022-03-16 Thread ASF GitHub Bot (Jira)


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

ASF GitHub Bot updated GEODE-10130:
---
Labels: GeodeOperationAPI pull-request-available  (was: GeodeOperationAPI)

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


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

2022-03-16 Thread Eric Shu (Jira)


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

Eric Shu updated GEODE-10130:
-
Labels: GeodeOperationAPI  (was: needsTriage)

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


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

2022-03-16 Thread Alexander Murmann (Jira)


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

Alexander Murmann updated GEODE-10130:
--
Labels: needsTriage  (was: )

> 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
>Priority: Major
>  Labels: needsTriage
>
> 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)