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

Hudson commented on FLUME-1819:
-------------------------------

Integrated in flume-trunk #398 (See 
[https://builds.apache.org/job/flume-trunk/398/])
    FLUME-1819. ExecSource must flush events to channel periodically. (Revision 
609a190e3f26462e540a0f25fdb56acd79af8ddc)

     Result = SUCCESS
hshreedharan : 
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=609a190e3f26462e540a0f25fdb56acd79af8ddc
Files : 
* flume-ng-core/src/test/java/org/apache/flume/source/TestExecSource.java
* 
flume-ng-core/src/main/java/org/apache/flume/source/ExecSourceConfigurationConstants.java
* flume-ng-core/src/main/java/org/apache/flume/source/ExecSource.java

                
> 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
>            Assignee: Venkatesh Sivasubramanian
>             Fix For: v1.4.0
>
>         Attachments: FLUME-1819-3.patch, FLUME-1819.patch, 
> FLUME-1819.patch.1, FLUME-1819.patch.2
>
>
> 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

Reply via email to