hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jakob Homan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-1054) Remove unnecessary sleep after failure in nextBlockOutputStream
Date Sun, 25 Apr 2010 01:43:50 GMT

    [ https://issues.apache.org/jira/browse/HDFS-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860625#action_12860625
] 

Jakob Homan commented on HDFS-1054:
-----------------------------------

Patch looks good except for unnecessary changes to log output (combining two log entries into
one).  We've not nailed down the log output format yet, but there's still no need to change
it without need, in case someone is currently parsing its output.

> 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
>         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.


Mime
View raw message