[ https://issues.apache.org/jira/browse/HDFS-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14122547#comment-14122547 ]
Hadoop QA commented on HDFS-6995: --------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12666662/HDFS-6995-002.patch against trunk revision 6104520. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 2 new or modified test files. {color:red}-1 javac{color}. The applied patch generated 1264 javac compiler warnings (more than the trunk's current 1215 warnings). {color:red}-1 javadoc{color}. The javadoc tool appears to have generated 9 warning messages. See https://builds.apache.org/job/PreCommit-HDFS-Build/7909//artifact/trunk/patchprocess/diffJavadocWarnings.txt for details. {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:red}-1 core tests{color}. The patch failed these unit tests in hadoop-hdfs-project/hadoop-hdfs: org.apache.hadoop.hdfs.server.namenode.ha.TestPipelinesFailover The following test timeouts occurred in hadoop-hdfs-project/hadoop-hdfs: org.apache.hadoop.hdfs.server.balancer.TestBalancTests org.apache.hadoop.hdfs.server.datanode.TestMultipleNNDataBlockScanner {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/7909//testReport/ Javac warnings: https://builds.apache.org/job/PreCommit-HDFS-Build/7909//artifact/trunk/patchprocess/diffJavacWarnings.txt Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/7909//console This message is automatically generated. > Block should be placed in the client's 'rack-local' node if 'client-local' > node is not available > ------------------------------------------------------------------------------------------------ > > Key: HDFS-6995 > URL: https://issues.apache.org/jira/browse/HDFS-6995 > Project: Hadoop HDFS > Issue Type: Bug > Components: namenode > Affects Versions: 2.5.0 > Reporter: Vinayakumar B > Assignee: Vinayakumar B > Attachments: HDFS-6995-001.patch, HDFS-6995-002.patch > > > HDFS cluster is rack aware. > Client is in different node than of datanode, > but Same rack contains one or more datanodes. > In this case first preference should be given to select 'rack-local' node. > Currently, since no Node in clusterMap corresponds to client's location, > blockplacement policy choosing a *random* node as local node and proceeding > for further placements. -- This message was sent by Atlassian JIRA (v6.3.4#6332)