[
https://issues.apache.org/jira/browse/FLUME-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14949211#comment-14949211
]
Hari Shreedharan commented on FLUME-2712:
-----------------------------------------
In general, the idea looks ok. But there is one problem with this patch - the
ordering of events in the optional channel is now messed up, since we are using
a thread pool to do so. This is true even if there is exactly one source. This
is a pretty obvious regression. I think we'd need to ensure ordering by
actually having a single thread submitting the events - we should keep a
blocking queue and have the thread poll that queue.
> Optional channel errors slows down the Source to Main channel event rate
> ------------------------------------------------------------------------
>
> Key: FLUME-2712
> URL: https://issues.apache.org/jira/browse/FLUME-2712
> Project: Flume
> Issue Type: Bug
> Reporter: Johny Rufus
> Assignee: Johny Rufus
> Attachments: FLUME-2712.patch, FLUME-2712.patch
>
>
> When we have a source configured to deliver events to a main channel and an
> optional channel, and if the delivery to optional channel fails, this
> significantly slows down the rate at which events are delivered to the main
> channel by the source.
> We need to evaluate async means of delivering events to the optional channel
> and isolate the errors happening in optional channel from the delivery to the
> main channel
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
