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

Guanghao Zhang commented on HBASE-15529:
----------------------------------------

Attach a v3 patch.

TestRegionRebalanceing failed because the default minCostNeedBalance is 0.05. 
So I set the config before this ut to fix this.

The reason of TestStochasticLoadBalancer2.testRegionReplicasOnMidCluster failed 
is same with previous 
TestStochasticLoadBalancer2#testRegionReplicasOnLargeCluster. The balancer 
can't total balance in the max running time. So it need add config before test, 
too.



> Override needBalance in StochasticLoadBalancer
> ----------------------------------------------
>
>                 Key: HBASE-15529
>                 URL: https://issues.apache.org/jira/browse/HBASE-15529
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Guanghao Zhang
>            Assignee: Guanghao Zhang
>            Priority: Minor
>             Fix For: 2.0.0, 1.4.0
>
>         Attachments: 15529-v1.patch, HBASE-15529-v1.patch, 
> HBASE-15529-v2.patch, HBASE-15529.patch
>
>
> StochasticLoadBalancer includes cost functions to compute the cost of region 
> rount, r/w qps, table load, region locality, memstore size, and storefile 
> size. Every cost function returns a number between 0 and 1 inclusive and the 
> computed costs are scaled by their respective multipliers. The bigger 
> multiplier means that the respective cost function have the bigger weight. 
> But needBalance decide whether to balance only by region count and doesn't 
> consider r/w qps, locality even you config these cost function with bigger 
> multiplier. StochasticLoadBalancer should override needBalance and decide 
> whether to balance by it's configs of cost functions.
> Add one new config hbase.master.balancer.stochastic.minCostNeedBalance, 
> cluster need balance when (total cost / sum multiplier) > minCostNeedBalance.



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

Reply via email to