[jira] [Updated] (GEODE-404) Using AttributesMutator.addAsyncEventQueueId in a system with concurrent operations will cause failures

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

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

Darrel Schneider updated GEODE-404:
-----------------------------------
    Component/s:     (was: core)
                 wan

> Using AttributesMutator.addAsyncEventQueueId in a system with concurrent operations will cause failures
> -------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-404
>                 URL: https://issues.apache.org/jira/browse/GEODE-404
>             Project: Geode
>          Issue Type: Bug
>          Components: wan
>            Reporter: Dan Smith
>
> It's possible to add an async event queue after a region is created using AttributesMutator.addAsyncEventQueueId.
> However, this code appears to have some issues if there are concurrent operations executing. Every put goes through  LocalRegion.checkSameSenderIdsAvailableOnAllNodes. This method will throw an exception if the async queue is not added on all nodes.
> Since the AsyncEventQueue will not be added at exactly the same time on all nodes, there will be a window of time when puts will throw exceptions when adding an AsyncEventQueue.
> In addition, this may be intentional, but *new* members that join a system *must* have the AEQ defined in their region attributes before creating the region. They cannot add the AEQ later. So the mutator is not useful as part of the initialization of a member.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)