[
https://issues.apache.org/jira/browse/FLUME-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13549429#comment-13549429
]
André Stein commented on FLUME-1819:
------------------------------------
Hi there.
I played around a bit with 1.3.1 and also found the behaviour this bug
addresses to. Thanks for the patch.
But I think there's another related issue to this: When stopping the
application, it may happen that there are still events in the cache
("eventList") that are never flushed and therefore lost. Looking at the code
strengthens this suspicion. Am I right and should I open a new issue for this
behavior?
Regards,
--
André
> ExecSource don't flush the cache if there is no input entries
> -------------------------------------------------------------
>
> Key: FLUME-1819
> URL: https://issues.apache.org/jira/browse/FLUME-1819
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources
> Affects Versions: v1.3.0
> Reporter: Fengdong Yu
> Fix For: v1.4.0
>
> Attachments: FLUME-1819.patch
>
>
> ExecSource has a default batchSize: 20, exec source read data from the
> source, then put it into the cache, after the cache is full, push it to the
> channel.
> but if exec source's cache is not full, and there isn't any input for a long
> time, then these entries always kept in the cache, there is no chance to the
> channel until the source's cache is full.
> so, the patch added a new config line: batchTimeout for ExecSource, and
> default is 3 seconds, if batchTimeout exceeded, push all cached data to the
> channel even the cache is not full.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
