[jira] [Resolved] (GEODE-6866) gateway sender/async event queue consistency check can cause write ops to be applied to region but left out of queue

["Darrel Schneider (JIRA)" <ji...@apache.org>]

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

Darrel Schneider resolved GEODE-6866.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.10.0

> gateway sender/async event queue consistency check can cause write ops to be applied to region but left out of queue
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-6866
>                 URL: https://issues.apache.org/jira/browse/GEODE-6866
>             Project: Geode
>          Issue Type: Bug
>          Components: wan
>            Reporter: Darrel Schneider
>            Priority: Major
>             Fix For: 1.10.0
>
>
> After a write operation has modified a region a check is done to see if the gateway sender ids and async event queue ids are consistent across the entire cluster. If they are consistent then the event is added to the gateway/asyncEvent queue. But if they are  not consistent an exception is thrown. This will lead to items being in the region but never put in queue.
> So at this point, instead of throwing an exception, we should just log a warning about the inconsistent configuration and go ahead and deliver the event to the gateways/asyncEventQueues that we do have.



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