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 2018/04/05 21:21:00 UTC
[jira] [Commented] (GEODE-4942) Secondary Gateway Sender queue
after GII might leave some event un-drained
[ https://issues.apache.org/jira/browse/GEODE-4942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16427624#comment-16427624 ]
ASF subversion and git services commented on GEODE-4942:
--------------------------------------------------------
Commit b5bb4b993f87289f0eb98339643968a82f2c6d9f in geode's branch refs/heads/feature/GEODE-4942 from zhouxh
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=b5bb4b9 ]
GEODE-4942: when sender is starting, and not running yet, put event at primary should be saved for QueueRemovalMessage
> Secondary Gateway Sender queue after GII might leave some event un-drained
> --------------------------------------------------------------------------
>
> Key: GEODE-4942
> URL: https://issues.apache.org/jira/browse/GEODE-4942
> Project: Geode
> Issue Type: Bug
> Components: wan
> Reporter: xiaojian zhou
> Assignee: xiaojian zhou
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We found this problem in #49196. It has been fixed several times. I just reproduced another scenario via
> ParallelGatewaySenderOperationsDUnitTest.
> testParallelPropagationSenderStartAfterStop_Scenario2.
> The test did not check the drain of secondary queue, if added the checking. sometime it will fail with some event stay in secondary queue forever.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)