hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HDFS-1054) Remove unnecessary sleep after failure in nextBlockOutputStream
Date Fri, 11 Jun 2010 23:45:15 GMT

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

dhruba borthakur resolved HDFS-1054.
------------------------------------

    Fix Version/s: 0.21.0
                       (was: 0.20-append)
       Resolution: Fixed

I committed it into the hadoop-0.20-append branch (as indicated by the affected version) but
reverted the fix-version to the original value of 0.21.

> 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-append, 0.20.3, 0.21.0, 0.22.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>             Fix For: 0.21.0
>
>         Attachments: 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message