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

Elliott Clark commented on HBASE-6143:
--------------------------------------

bq.Regions are not rebalanced based on locality
Trunk should already have locality awareness built in.  Since not every file 
will be created on the same set of datanodes it will be hard to have 100% until 
the favored nodes functionality is in a shipped version of HDFS.

https://github.com/apache/hbase/blob/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/balancer/StochasticLoadBalancer.java#L524



bq.0.94.6
HBASE-9080 was opened up for 0.94 branch, to deal with the full restart case.  
But like [~lhofhansl] said in 0.94 the balancer doesn't know about locality so 
the only way to get it for sure is to have compactions run (either minor or 
major).
                
> Make region assignment smarter when regions are re-enabled.
> -----------------------------------------------------------
>
>                 Key: HBASE-6143
>                 URL: https://issues.apache.org/jira/browse/HBASE-6143
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Elliott Clark
>            Assignee: Ted Yu
>            Priority: Critical
>             Fix For: 0.95.2
>
>         Attachments: 6143-v1.txt, 6143-v2.txt, 6143-v3.txt, 
> HBASE-6143-0.patch, HBASE-6143-1.patch
>
>
> Right now a random region server is picked when re-enabling a table. This 
> could be much smarter.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to