You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2010/03/21 09:11:27 UTC
[jira] Created: (HDFS-1054) Make sleep after failure in
nextBlockOutputStream smarter and configurable
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
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.
[jira] Reopened: (HDFS-1054) Remove unnecessary sleep after failure
in nextBlockOutputStream
Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon reopened HDFS-1054:
-------------------------------
Reopening for commit to append 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.22.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Fix For: 0.20-append
>
> Attachments: 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.
[jira] Resolved: (HDFS-1054) Remove unnecessary sleep after failure
in nextBlockOutputStream
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ 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.