[
https://issues.apache.org/jira/browse/FLUME-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13589255#comment-13589255
]
Mike Percy commented on FLUME-1916:
-----------------------------------
Added a patch that accomplishes this. The test is racy so we check for either 4
or 5 files, since we don't know whether the client notices that we killed a DN
until it calls sync(). Sometimes it notices before that, sometimes it notices
at that time.
Also added a param to allow for manually specifying the minimum replication
factor we want to allow before a file roll. The default is the default
replication factor.
The nasty reflection stuff was directly purloined from HBASE-2234. :)
> HDFS sink should poll for # of active replicas. If less than required, roll
> the file.
> -------------------------------------------------------------------------------------
>
> Key: FLUME-1916
> URL: https://issues.apache.org/jira/browse/FLUME-1916
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources
> Affects Versions: v1.3.1
> Reporter: Mike Percy
> Assignee: Mike Percy
> Fix For: v1.4.0
>
> Attachments: FLUME-1916.patch
>
>
> Add functionality to the HDFS sink which constantly polls the number of
> replicas for files being written. If the number of replicas drops below 3 (or
> specified number), it should immediately close the HDFS output file and start
> a new file that should be able to create a pipeline with the correct number
> of replicas.
> This is the same behavior taken by HBase for its write-ahead log (WAL) and
> should help us avoid hitting the more complex corner cases around failed
> close() calls.
--
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
