You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Venkatesh Sivasubramanian (JIRA)" <ji...@apache.org> on 2013/04/18 19:05:16 UTC

[jira] [Commented] (FLUME-1819) ExecSource don't flush the cache if there is no input entries

    [ https://issues.apache.org/jira/browse/FLUME-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635348#comment-13635348 ] 

Venkatesh Sivasubramanian commented on FLUME-1819:
--------------------------------------------------

Hi Hari: We have a need for this fix. I would like to work on this and take it to completion, if that is fine with all. I can work on the FLUME-1837 issue as well in parallel.

Pls. let me know.


                
> 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