hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HDFS-1054) Make sleep after failure in nextBlockOutputStream smarter and configurable
Date Mon, 05 Apr 2010 03:51:27 GMT

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

Todd Lipcon updated HDFS-1054:

    Attachment: hdfs-1054.txt

Here's a patch which removes the sleep altogether. I looked through the svn logs and this
sleep has been there since Nutch, and I can't think of any particular reason why it's useful.

If someone can think of a time when it actually is a good idea to sleep, I'll upload a patch
that makes it configurable, but otherwise I think we should just remove it.

> Make sleep after failure in nextBlockOutputStream smarter and configurable
> --------------------------------------------------------------------------
>                 Key: HDFS-1054
>                 URL: https://issues.apache.org/jira/browse/HDFS-1054
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: hdfs client
>    Affects Versions: 0.22.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>         Attachments: 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.

View raw message