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

Hudson commented on HDFS-8826:
------------------------------

FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #289 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/289/])
HDFS-8826. In Balancer, add an option to specify the source node list so that 
balancer only selects blocks to move from those nodes. (szetszwo: rev 
7ecbfd44aa57f5f54c214b7fdedda2500be76f51)
* 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/balancer/Dispatcher.java
* 
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/StringUtils.java
* 
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/balancer/TestBalancer.java
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/HostsFileReader.java
* 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/balancer/Balancer.java


> Balancer may not move blocks efficiently in some cases
> ------------------------------------------------------
>
>                 Key: HDFS-8826
>                 URL: https://issues.apache.org/jira/browse/HDFS-8826
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: balancer & mover
>            Reporter: Tsz Wo Nicholas Sze
>            Assignee: Tsz Wo Nicholas Sze
>             Fix For: 2.8.0
>
>         Attachments: h8826_20150811.patch, h8826_20150816.patch, 
> h8826_20150818.patch
>
>
> Balancer is inefficient in the following case:
> || Datanode || Utilization || Rack ||
> | D1 | 95% | A |
> | D2 | 30% | B |
> | D3, D4, D5 | 0% | B |
> The average utilization is 25% so that D2 is within 10% threshold.  However, 
> Balancer currently will first move blocks from D2 to D3, D4 and D5 since they 
> are under the same rack.  Then, it will move blocks from D1.



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

Reply via email to