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

Hudson commented on FLUME-1238:
-------------------------------

Integrated in flume-trunk #227 (See 
[https://builds.apache.org/job/flume-trunk/227/])
    FLUME-1238. Support active rolling of files created by HDFS Event Sink.

(Mike Percy via Arvind Prabhakar) (Revision 1347216)

     Result = SUCCESS
arvind : http://svn.apache.org/viewvc/?view=rev&rev=1347216
Files : 
* /incubator/flume/trunk/flume-ng-doc/sphinx/FlumeUserGuide.rst
* 
/incubator/flume/trunk/flume-ng-sinks/flume-hdfs-sink/src/main/java/org/apache/flume/sink/hdfs/BucketWriter.java
* 
/incubator/flume/trunk/flume-ng-sinks/flume-hdfs-sink/src/main/java/org/apache/flume/sink/hdfs/HDFSEventSink.java
* 
/incubator/flume/trunk/flume-ng-sinks/flume-hdfs-sink/src/test/java/org/apache/flume/sink/hdfs/MockHDFSWriter.java
* 
/incubator/flume/trunk/flume-ng-sinks/flume-hdfs-sink/src/test/java/org/apache/flume/sink/hdfs/TestBucketWriter.java

                
> Support active rolling of files created by HDFS Event Sink
> ----------------------------------------------------------
>
>                 Key: FLUME-1238
>                 URL: https://issues.apache.org/jira/browse/FLUME-1238
>             Project: Flume
>          Issue Type: Improvement
>    Affects Versions: v1.1.0
>            Reporter: Arvind Prabhakar
>            Assignee: Mike Percy
>             Fix For: v1.2.0
>
>         Attachments: FLUME-1238-1.patch, FLUME-1238-2.patch
>
>
> The HDFS Event Sink uses lazy rolling for closing files that are being 
> written to. This results in many files being open for longer than their 
> expected roll-interval if they are not actively written to and can even last 
> in open state until the sink shuts down.
> It will be preferable to have these files roll proactively rather than 
> waiting for a write to trigger the roll. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to