[
https://issues.apache.org/jira/browse/GEODE-8324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17213425#comment-17213425
]
ASF subversion and git services commented on GEODE-8324:
--------------------------------------------------------
Commit be100b3534037b22d8dae6c145fc710eb3b99726 in geode's branch
refs/heads/feature/GEODE-8324 from Barry Oglesby
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=be100b3 ]
GEODE-8324: Don't add a remote ds id to recipients unless it is running
> Events are not being replicated from one WAN site to another when there are
> multiple paths between the sites and the direct one is stopped
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: GEODE-8324
> URL: https://issues.apache.org/jira/browse/GEODE-8324
> Project: Geode
> Issue Type: Bug
> Components: wan
> Reporter: Barrett Oglesby
> Assignee: Barrett Oglesby
> Priority: Major
> Labels: caching-applications, pull-request-available
>
> Scenario
> --------
> The configuration is a normal star/mesh pattern where each site is connected
> to each other site.
> So, there are 2 paths from site-A to site-B:
> - the direct (site-A -> site-B)
> - the indirect path (site-A -> site-C -> site-B)
> If the direct path (meaning the sender in site-A to site-B) is stopped and a
> put is done in site-A, site-B doesn't receive the event even though the
> indirect path is not stopped.
> Here is the behavior:
> Site-A - dsid=1
> Site-B - dsid=2
> Site-C - dsid=3
> Site-A
> ------
> Since site-A is configured with site-B and site-C, its events will contain
> recipient dsids for those sites (2 and 3 below).
> The event sent to site-C will look like:
> {noformat}
> AbstractGatewaySender.distribute sender=site-C processing local event
> newCallbackArg=GatewaySenderEventCallbackArgument
> [originatingSenderId=1;recipientGatewayReceivers={3, 2}]; region=/data; key=0
> {noformat}
> Site-C
> ------
> Site-C receives the event:
> {noformat}
> GatewayReceiverCommand.cmdExecute processing create region=/data; key=0
> {noformat}
> The sender to site-B drops the event since it thinks it is already a
> recipient:
> {noformat}
> AbstractGatewaySender.distribute sender=site-B received event from remote
> site receivedCallbackArg=GatewaySenderEventCallbackArgument
> [originatingSenderId=1;recipientGatewayReceivers={3, 2}]; region=/data;
> key=0; eventId=EventID[id=25
> bytes;threadID=0x10030|1;sequenceID=0;bucketId=48]
> AbstractGatewaySender.distribute sender=site-B dropping event since it is
> already a recipient
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
