[ https://issues.apache.org/jira/browse/HDFS-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174990#comment-14174990 ]
Uma Maheswara Rao G commented on HDFS-6995: ------------------------------------------- I am in the business trip to US. Expect my delayed responses in this period. > 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 > Fix For: 2.6.0 > > Attachments: HDFS-6995-001.patch, HDFS-6995-002.patch, > HDFS-6995-003.patch, HDFS-6995-004.patch, HDFS-6995-005.patch, > HDFS-6995-006.patch, HDFS-6995-007.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)