[
https://issues.apache.org/jira/browse/HDFS-6755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14075050#comment-14075050
]
Hudson commented on HDFS-6755:
------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #5971 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/5971/])
HDFS-6755. There is an unnecessary sleep in the code path where
DFSOutputStream#close gives up its attempt to contact the namenode (mitdesai21
via cmccabe) (cmccabe:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1613522)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSOutputStream.java
> There is an unnecessary sleep in the code path where DFSOutputStream#close
> gives up its attempt to contact the namenode
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-6755
> URL: https://issues.apache.org/jira/browse/HDFS-6755
> Project: Hadoop HDFS
> Issue Type: Improvement
> Affects Versions: 2.6.0
> Reporter: Mit Desai
> Assignee: Mit Desai
> Attachments: HDFS-6755.patch
>
>
> DFSOutputStream#close has a loop where it tries to contact the NameNode, to
> call {{complete}} on the file which is open-for-write. This loop includes a
> sleep which increases exponentially (exponential backoff). It makes sense to
> sleep before re-contacting the NameNode, but the code also sleeps even in the
> case where it has already decided to give up and throw an exception back to
> the user. It should not sleep after it has already decided to give up, since
> there's no point.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
