[jira] [Commented] (HDFS-2637) The rpc timeout for block recovery is too low
[ https://issues.apache.org/jira/browse/HDFS-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13164100#comment-13164100 ] Uma Maheswara Rao G commented on HDFS-2637: --- Ok Todd, i will take a look on trunk code once and update if it really applies. Why i pointed for trunk is because HDFS-2378 filed against to 0.23.0 and 1.1.0. > 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
[jira] [Commented] (HDFS-2637) The rpc timeout for block recovery is too low
[ 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
[jira] [Commented] (HDFS-2637) The rpc timeout for block recovery is too low
[ https://issues.apache.org/jira/browse/HDFS-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13164091#comment-13164091 ] Uma Maheswara Rao G commented on HDFS-2637: --- This may be applicable for trunk as well right? I think this issue is same as HDFS-2378. Can it be duplicated? > 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
[jira] [Commented] (HDFS-2637) The rpc timeout for block recovery is too low
[ https://issues.apache.org/jira/browse/HDFS-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13164059#comment-13164059 ] Todd Lipcon commented on HDFS-2637: --- +1 > 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
[jira] [Commented] (HDFS-2637) The rpc timeout for block recovery is too low
[
https://issues.apache.org/jira/browse/HDFS-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13164025#comment-13164025
]
Eli Collins commented on HDFS-2637:
---
Unit tests are running, earlier run was clean. test-patch results follow. 4
findbugs warnings are HADOOP-7847, not this patch.
{noformat}
[exec]
[exec] -1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] -1 tests included. The patch doesn't appear to include any new
or modified tests.
[exec] Please justify why no tests are needed for
this patch.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number
of javac compiler warnings.
[exec]
[exec] -1 findbugs. The patch appears to introduce 4 new Findbugs
(version 1.3.9) warnings.
[exec]
{noformat}
> 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
