[
https://issues.apache.org/jira/browse/HBASE-25769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412231#comment-17412231
]
Clara Xiong commented on HBASE-25769:
-------------------------------------
[~Xiaolin Ha] More updates for byTable option. We have seen it enabled on a
different large cluster ( close to 1000 RS )which worked poorly too. By table
works fine with many small tables and with at most a large table on a large
cluster. The fix in https://issues.apache.org/jira/browse/HBASE-25739 make
tableSkewCostFunction finally work and we switched to rely on it by increasing
its weight other than by table option.
> Update default weight of cost functions
> ---------------------------------------
>
> Key: HBASE-25769
> URL: https://issues.apache.org/jira/browse/HBASE-25769
> Project: HBase
> Issue Type: Sub-task
> Components: Balancer
> Reporter: Clara Xiong
> Priority: Major
>
> In production, we have seen some critical big tables that handle majority of
> the load. Table Skew is becoming more important. With the update of table
> skew function, balancer finally works for large table distribution on large
> cluster. We should increase the weight from 35 to a level comparable to
> region count skew: 500. We can even push further to replace region count skew
> by table skew since the latter works in the same way and account for region
> distribution per node.
> Another weight we found helpful to increase is for store file size cost
> function. Ideally if normalizer works perfectly, we don't need to worry about
> it since region count skew would have accounted for it. But we are often in a
> situation it doesn't. Store file distribution needs to be given more way as
> accommodation. we tested changing it from 5 to 200 and it works fine.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
