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) Remove unnecessary sleep after failure in nextBlockOutputStream
Date Fri, 11 Jun 2010 23:32:14 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-0.20-append.txt

Attaching patch for 0.20-append branch. It's just slightly different than what went into trunk
(did less cleanup to minimize change). No unit test but has been cluster tested for last several
months with lots of failure testing.

> 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.22.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>             Fix For: 0.20-append
>
>         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