[ https://issues.apache.org/jira/browse/HDFS-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139967#comment-14139967 ]
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/12669760/HDFS-6995-003.patch against trunk revision 6434572. {color:red}-1 patch{color}. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/8099//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-6995-003.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)