[ https://issues.apache.org/jira/browse/HDFS-6247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14094079#comment-14094079 ]
Hadoop QA commented on HDFS-6247: --------------------------------- {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12661168/HDFS-6247.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 1 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. There were no new javadoc warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 2.0.3) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in hadoop-hdfs-project/hadoop-hdfs. {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/7615//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/7615//console This message is automatically generated. > Avoid timeouts for replaceBlock() call by sending intermediate responses to > Balancer > ------------------------------------------------------------------------------------ > > Key: HDFS-6247 > URL: https://issues.apache.org/jira/browse/HDFS-6247 > Project: Hadoop HDFS > Issue Type: Bug > Components: balancer, datanode > Affects Versions: 2.4.0 > Reporter: Vinayakumar B > Assignee: Vinayakumar B > Attachments: HDFS-6247.patch, HDFS-6247.patch, HDFS-6247.patch, > HDFS-6247.patch, HDFS-6247.patch, HDFS-6247.patch, HDFS-6247.patch, > HDFS-6247.patch > > > Currently there is no response sent from target Datanode to Balancer for the > replaceBlock() calls. > Since the Block movement for balancing is throttled, complete block movement > will take time and this could result in timeout at Balancer, which will be > trying to read the status message. > > To Avoid this during replaceBlock() call in in progress Datanode can send > IN_PROGRESS status messages to Balancer to avoid timeouts and treat > BlockMovement as failed. -- This message was sent by Atlassian JIRA (v6.2#6252)