[
https://issues.apache.org/jira/browse/FLUME-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15611633#comment-15611633
]
ASF subversion and git services commented on FLUME-2997:
--------------------------------------------------------
Commit 7c4b2fd3e88f038dea3bdae01eb864547770ad48 in flume's branch
refs/heads/trunk from [~sati]
[ https://git-wip-us.apache.org/repos/asf?p=flume.git;h=7c4b2fd ]
FLUME-2997. Fix flaky test in SpillableMemoryChannel
When the mock sinks are slower than sources, testParallelSingleSourceAndSink
sometimes fails.
In such situations the channel can get full, thus uncaught ChannelFullException
breaks the test.
Since testCapacityWithOverflow was designed to cover such a scenario, we
can safely fix the test by increasing the channel capacity to make sure it
won't get full.
This commit does the previously mentioned change.
Reviewers: Bessenyei Balázs Donát
(Attila Simon via Bessenyei Balázs Donát)
> Fix flaky junit test in SpillableMemoryChannel
> ----------------------------------------------
>
> Key: FLUME-2997
> URL: https://issues.apache.org/jira/browse/FLUME-2997
> Project: Flume
> Issue Type: Test
> Affects Versions: v1.7.0
> Reporter: Attila Simon
> Assignee: Attila Simon
> Fix For: v1.8.0
>
> Attachments: FLUME-2997-1.patch, FLUME-2997.patch
>
>
> testParallelSingleSourceAndSink sometimes trigger an edge case scenario if
> sinks are slower than sources. In such situations the channel can get full
> thus uncaught ChannelFullException breaks the test. Since
> testCapacityWithOverflow was designed to cover such edge-case scenario
> already we can safely fix the test by increasing the channel capacity to make
> sure it won't get full.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
