You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Dick Cavender (Jira)" <ji...@apache.org> on 2019/12/07 00:14:00 UTC
[jira] [Updated] (GEODE-7473) when the sender is not ready, before
adding to tmpDroppedEvents, should check its destination dsid
[ https://issues.apache.org/jira/browse/GEODE-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dick Cavender updated GEODE-7473:
---------------------------------
Fix Version/s: 1.11.0
> when the sender is not ready, before adding to tmpDroppedEvents, should check its destination dsid
> --------------------------------------------------------------------------------------------------
>
> Key: GEODE-7473
> URL: https://issues.apache.org/jira/browse/GEODE-7473
> Project: Geode
> Issue Type: Bug
> Reporter: Xiaojian Zhou
> Priority: Major
> Fix For: 1.11.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> When WAN receiver received an event, if its region also defined a sender, it will check event's GatewaySenderEventCallbackArgument's dsIds to see if it should be filtered out.
> WAN used this logic to prevent the event from bouncing back to wrong site, such as original sender.
> In GEODE-5087's fix, when found sender is not available and add to tmpDroppedEvents before checking event's GatewaySenderEventCallbackArgument. This should be done after checking GatewaySenderEventCallbackArgument.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)