[ 
https://issues.apache.org/jira/browse/HDFS-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14160214#comment-14160214
 ] 

Hudson commented on HDFS-6995:
------------------------------

FAILURE: Integrated in Hadoop-Yarn-trunk #703 (See 
[https://builds.apache.org/job/Hadoop-Yarn-trunk/703/])
HDFS-6995. Block should be placed in the client's 'rack-local' node if 
'client-local' node is not available (vinayakumarb) (vinayakumarb: rev 
ed841dd9a96e54cb84d9cae5507e47ff1c8cdf6e)
* 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/BlockPlacementPolicyDefault.java
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/blockmanagement/TestReplicationPolicyConsiderLoad.java
* 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
* 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/DatanodeManager.java
* 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/BlockManager.java


> 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)

Reply via email to