hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Chu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-6755) There is an unnecessary sleep in the code path where DFSOutputStream#close gives up its attempt to contact the namenode
Date Mon, 28 Jul 2014 04:27:39 GMT

     [ https://issues.apache.org/jira/browse/HDFS-6755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Stephen Chu updated HDFS-6755:
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.6.0
                   3.0.0
           Status: Resolved  (was: Patch Available)

> 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
>             Fix For: 3.0.0, 2.6.0
>
>         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)

Mime
View raw message