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 2017/09/25 18:01:00 UTC

[jira] [Commented] (GEODE-3678) When a member is lost, gateway sender queues are not synchronized with surviving members

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

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

Commit af4012f5f934c7e8f21025c528d8ba18e3aad794 in geode's branch refs/heads/develop from [~barry.oglesby]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=af4012f ]

GEODE-3678: Added support to synchronize parallel gateway sender queues


> When a member is lost, gateway sender queues are not synchronized with surviving members
> ----------------------------------------------------------------------------------------
>
>                 Key: GEODE-3678
>                 URL: https://issues.apache.org/jira/browse/GEODE-3678
>             Project: Geode
>          Issue Type: Bug
>          Components: wan
>            Reporter: Barry Oglesby
>            Assignee: Barry Oglesby
>
> DistributedRegion synchronizeForLostMember is invoked in each surviving member. This method synchronizes the region with all replicates as long as concurrency checks are enabled for that region. Concurrency checks are disabled for GatewaySender queue regions so they don't get synchronized.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)