[
https://issues.apache.org/jira/browse/HDFS-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13164093#comment-13164093
]
Todd Lipcon commented on HDFS-2637:
-----------------------------------
doh, yea, this is dup of HDFS-2378. Somehow when Eli and I were discussing it
this morning I forgot that I'd already filed a JIRA for it. Since we already
have the patch here, we can just commit this one and mark the other as dup, I
guess?
In trunk the block recovery algorithm is quite different so I don't think it
applies -- the block recovery is triggered as part of the pipeline setup,
rather than an RPC. But maybe we have a similar type of bug in trunk with
timeouts in the pipeline setup process? Mind taking a look, Uma?
> The rpc timeout for block recovery is too low
> ----------------------------------------------
>
> Key: HDFS-2637
> URL: https://issues.apache.org/jira/browse/HDFS-2637
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs client
> Affects Versions: 1.0.0
> Reporter: Eli Collins
> Assignee: Eli Collins
> Attachments: hdfs-2637-b1-1.patch
>
>
> The RPC timeout for block recovery does not take into account that it issues
> multiple RPCs itself. This can cause recovery to fail if the network is
> congested or DNs are busy.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
