hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-1054) Remove unnecessary sleep after failure in nextBlockOutputStream
Date Fri, 02 Sep 2011 21:54:10 GMT

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

Suresh Srinivas updated HDFS-1054:
----------------------------------

    Fix Version/s: 0.20.205.0

+1 for the patch. I committed the patch to 0.20-security branch.

> Remove unnecessary sleep after failure in nextBlockOutputStream
> ---------------------------------------------------------------
>
>                 Key: HDFS-1054
>                 URL: https://issues.apache.org/jira/browse/HDFS-1054
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: hdfs client
>    Affects Versions: 0.20.3, 0.20-append, 0.21.0, 0.22.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>             Fix For: 0.20-append, 0.20.205.0, 0.21.0
>
>         Attachments: HDFS-1054.20-security.1.patch, hdfs-1054-0.20-append.txt, hdfs-1054.txt,
hdfs-1054.txt
>
>
> If DFSOutputStream fails to create a pipeline, it currently sleeps 6 seconds before retrying.
I don't see a great reason to wait at all, much less 6 seconds (especially now that HDFS-630
ensures that a retry won't go back to the bad node). We should at least make it configurable,
and perhaps something like backoff makes some sense.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message