[jira] [Commented] (GEODE-8324) 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
[
https://issues.apache.org/jira/browse/GEODE-8324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17278530#comment-17278530
]
ASF GitHub Bot commented on GEODE-8324:
---
onichols-pivotal commented on pull request #5331:
URL: https://github.com/apache/geode/pull/5331#issuecomment-773029200
This PR has been inactive for some while, can it be closed?
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> 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)
[jira] [Commented] (GEODE-8324) 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
[
https://issues.apache.org/jira/browse/GEODE-8324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215640#comment-17215640
]
ASF subversion and git services commented on GEODE-8324:
Commit 23cfacff6cc875830416c11c0ccaaaebf15d36d2 in geode's branch
refs/heads/feature/GEODE-8324 from Barry Oglesby
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=23cfacf ]
GEODE-8324: Updated dunit test
> 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)
[jira] [Commented] (GEODE-8324) 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
[
https://issues.apache.org/jira/browse/GEODE-8324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215587#comment-17215587
]
ASF subversion and git services commented on GEODE-8324:
Commit f57dea3f3633bdc749f16649d6ce4dbef1fcf752 in geode's branch
refs/heads/feature/GEODE-8324 from Barry Oglesby
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=f57dea3 ]
GEODE-8324: Added dunit test
> 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)
[jira] [Commented] (GEODE-8324) 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
[
https://issues.apache.org/jira/browse/GEODE-8324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215584#comment-17215584
]
ASF subversion and git services commented on GEODE-8324:
Commit f57dea3f3633bdc749f16649d6ce4dbef1fcf752 in geode's branch
refs/heads/feature/GEODE-8324 from Barry Oglesby
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=f57dea3 ]
GEODE-8324: Added dunit test
> 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)
[jira] [Commented] (GEODE-8324) 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
[
https://issues.apache.org/jira/browse/GEODE-8324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215583#comment-17215583
]
ASF subversion and git services commented on GEODE-8324:
Commit f57dea3f3633bdc749f16649d6ce4dbef1fcf752 in geode's branch
refs/heads/feature/GEODE-8324 from Barry Oglesby
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=f57dea3 ]
GEODE-8324: Added dunit test
> 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)
[jira] [Commented] (GEODE-8324) 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
[
https://issues.apache.org/jira/browse/GEODE-8324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215580#comment-17215580
]
ASF subversion and git services commented on GEODE-8324:
Commit f57dea3f3633bdc749f16649d6ce4dbef1fcf752 in geode's branch
refs/heads/feature/GEODE-8324 from Barry Oglesby
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=f57dea3 ]
GEODE-8324: Added dunit test
> 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)
[jira] [Commented] (GEODE-8324) 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
[
https://issues.apache.org/jira/browse/GEODE-8324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215578#comment-17215578
]
ASF subversion and git services commented on GEODE-8324:
Commit f57dea3f3633bdc749f16649d6ce4dbef1fcf752 in geode's branch
refs/heads/feature/GEODE-8324 from Barry Oglesby
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=f57dea3 ]
GEODE-8324: Added dunit test
> 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)
[jira] [Commented] (GEODE-8324) 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
[
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)
[jira] [Commented] (GEODE-8324) 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
[
https://issues.apache.org/jira/browse/GEODE-8324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17213412#comment-17213412
]
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)
[jira] [Commented] (GEODE-8324) 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
[
https://issues.apache.org/jira/browse/GEODE-8324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17213401#comment-17213401
]
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)
[jira] [Commented] (GEODE-8324) 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
[
https://issues.apache.org/jira/browse/GEODE-8324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17213390#comment-17213390
]
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)
[jira] [Commented] (GEODE-8324) 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
[
https://issues.apache.org/jira/browse/GEODE-8324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17213378#comment-17213378
]
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)
[jira] [Commented] (GEODE-8324) 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
[
https://issues.apache.org/jira/browse/GEODE-8324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17204258#comment-17204258
]
ASF GitHub Bot commented on GEODE-8324:
---
onichols-pivotal commented on pull request #5331:
URL: https://github.com/apache/geode/pull/5331#issuecomment-700950619
last activity was some while ago, please close this PR if no longer needed
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> 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
>
> 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)
[jira] [Commented] (GEODE-8324) 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
[
https://issues.apache.org/jira/browse/GEODE-8324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17148966#comment-17148966
]
ASF subversion and git services commented on GEODE-8324:
Commit 514b17a5a43093c2301c5305ea356bc48924fe90 in geode's branch
refs/heads/feature/GEODE-8324 from Barry Oglesby
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=514b17a ]
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
>
> 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)
[jira] [Commented] (GEODE-8324) 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
[
https://issues.apache.org/jira/browse/GEODE-8324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17148967#comment-17148967
]
ASF GitHub Bot commented on GEODE-8324:
---
boglesby opened a new pull request #5331:
URL: https://github.com/apache/geode/pull/5331
Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced in
the commit message?
- [ ] Has your PR been rebased against the latest commit within the target
branch (typically `develop`)?
- [ ] Is your initial contribution a single, squashed commit?
- [ ] Does `gradlew build` run cleanly?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
### Note:
Please ensure that once the PR is submitted, check Concourse for build
issues and
submit an update to your PR as soon as possible. If you need help, please
send an
email to d...@geode.apache.org.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> 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
>
> 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)
