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

Hudson commented on HDFS-9036:
------------------------------

SUCCESS: Integrated in Hadoop-Yarn-trunk #1115 (See 
[https://builds.apache.org/job/Hadoop-Yarn-trunk/1115/])
HDFS-9036. In BlockPlacementPolicyWithNodeGroup#chooseLocalStorage , random 
node is selected eventhough fallbackToLocalRack is true. (Contributed by 
J.Andreina) (vinayakumarb: rev c7156503856e24faf844c5c647157b310d8b537f)
* 
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/blockmanagement/TestReplicationPolicyWithNodeGroup.java
* 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/BlockPlacementPolicyWithNodeGroup.java
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt


> In BlockPlacementPolicyWithNodeGroup#chooseLocalStorage , random node is 
> selected eventhough fallbackToLocalRack is true.
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-9036
>                 URL: https://issues.apache.org/jira/browse/HDFS-9036
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: J.Andreina
>            Assignee: J.Andreina
>             Fix For: 2.8.0
>
>         Attachments: HDFS-9036.1.patch, HDFS-9036.2.patch
>
>
> For example in below clusterMap
> Writer                         = "/d2/r4/n8" which does not have local node.
> Available nodes rack = {"/d2/r4/n7","/d1/r1/n1","/d1/r2/n3","/d2/r3/n6"}
> Current hierarchy in choosing node for first local storage replica is
>       1. Choose local machine (Not available)
>       2. Choose Local node group machine (Not available)
>       3. choose random
> *But instead of choosing random , should choose localrack node first(if 
> fallbackToLocalRack is true, in example it is "/d2/r4/n7" ) else should go 
> for radom node*



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to