[
https://issues.apache.org/jira/browse/HBASE-15515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15211268#comment-15211268
]
Guanghao Zhang commented on HBASE-15515:
----------------------------------------
Unit tests in TestStochasticLoadBalancer and TestStochasticLoadBalancer2 always
set hbase.master.balancer.stochastic.localityCost to 0. The unit tests didn't
think about region locality when balance cluster. Maybe we should add some
balancer unit tests about locality first.
> Improve LocalityBasedCandidateGenerator in Balancer
> ---------------------------------------------------
>
> Key: HBASE-15515
> URL: https://issues.apache.org/jira/browse/HBASE-15515
> Project: HBase
> Issue Type: Bug
> Affects Versions: 2.0.0, 1.3.0
> Reporter: Guanghao Zhang
> Assignee: Guanghao Zhang
> Priority: Minor
> Fix For: 2.0.0, 1.3.0, 1.4.0
>
> Attachments: HBASE-15515-v1.patch, HBASE-15515.patch
>
>
> There are some problems which need to fix.
> 1. LocalityBasedCandidateGenerator.getLowestLocalityRegionOnServer should
> skip empty region.
> 2. When use LocalityBasedCandidateGenerator to generate Cluster.Action, it
> should add random operation instead of pickLowestLocalityServer(cluster).
> Because the search function may stuck here if it always generate the same
> Cluster.Action.
> 3. getLeastLoadedTopServerForRegion should get least loaded server which have
> better locality than current server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
