[
https://issues.apache.org/jira/browse/HDFS-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860627#action_12860627
]
Todd Lipcon commented on HDFS-1054:
-----------------------------------
I combined the log entries because I think the bad datanode should be INFO
level. Would you prefer that I just change that message to INFO rather than
combining them at the same time? Given that the abandonment is a direct result
of the bad node, I think it makes more sense to have one message. Also, the
node exclusion log is from HDFS-630 which hasn't been released yet, so I don't
think we risk that anyone is parsing it.
> 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.
