Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
Description
With 3+ geo-red systems Geode replication has the forwarding feature which means that receiving cluster will forward the event it just got to all clusters it is connected to that have not yet received the event.
This is possible because the originating cluster is setting metadata in the replication event like this:
GatewaySenderEventCallbackArgument [originalCallbackArg=null;originatingSenderId=1;recipientGatewayReceivers= {3, 2}]
Site receiving this event thus knows which is the originating site and which sites should have received this event. All others will have this event forwarded to. All this is legacy Geode behavior.
However, originating site does not care if GW sender to a destination is stopped or not - only the fact GW sender is created and attached to a region is enough. This means if e.g. GW sender from Site1 to Site 3 is stopped (and has been stopped for a while - so this has nothing to do with timing) at the moment an event hits the replication it is only going to be sent to Site 2 but with the same metadata. Hence Site 2 will not forward to Site 3 (assuming it has a connection to it).
Attachments
Issue Links
- is duplicated by
-
GEODE-10212 In a WAN topology with 3 sites in a star pattern, stopping a sender between two of the sites causes an event to be dropped even though another path exists between the two sites
- Resolved
- links to