[
https://issues.apache.org/jira/browse/FLUME-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14295984#comment-14295984
]
Hudson commented on FLUME-2586:
-------------------------------
UNSTABLE: Integrated in flume-trunk #709 (See
[https://builds.apache.org/job/flume-trunk/709/])
FLUME-2586. HDFS Sink must try to rename files even if close fails.
(hshreedharan:
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=0d6eccad2781884fe0f000f74b8f964cbdd7971f)
*
flume-ng-sinks/flume-hdfs-sink/src/main/java/org/apache/flume/sink/hdfs/BucketWriter.java
*
flume-ng-sinks/flume-hdfs-sink/src/test/java/org/apache/flume/sink/hdfs/MockFsDataOutputStream.java
*
flume-ng-sinks/flume-hdfs-sink/src/test/java/org/apache/flume/sink/hdfs/TestBucketWriter.java
*
flume-ng-sinks/flume-hdfs-sink/src/test/java/org/apache/flume/sink/hdfs/TestHDFSEventSink.java
*
flume-ng-sinks/flume-hdfs-sink/src/test/java/org/apache/flume/sink/hdfs/MockFileSystem.java
> HDFS Sink should have an option to try rename even if close fails
> -----------------------------------------------------------------
>
> Key: FLUME-2586
> URL: https://issues.apache.org/jira/browse/FLUME-2586
> Project: Flume
> Issue Type: Bug
> Reporter: Johny Rufus
> Assignee: Johny Rufus
> Fix For: v1.6.0
>
> Attachments: FLUME-2586.patch
>
>
> "The issue is that the file close fails, but the stream on the Flume side is
> considered closed by HDFS. So retrying the close, is failing - which causes
> the rename never to be attempted. Since the rename is never attempted the
> file sticks around with the ".tmp" file name. "
> We should add a parameter "renameIfCloseFails", that will attempt rename even
> if the close fails and possibly log information that the user need to run
> lease recovery
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
