[ 
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

        

Reply via email to