You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/17 18:55:00 UTC

[jira] [Resolved] (HBASE-12928) BaseLoadBalancer#needsBalance only checks the sloppiness of region count before balancing

     [ https://issues.apache.org/jira/browse/HBASE-12928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Kyle Purtell resolved HBASE-12928.
-----------------------------------------
    Resolution: Incomplete

> BaseLoadBalancer#needsBalance only checks the sloppiness of region count before balancing
> -----------------------------------------------------------------------------------------
>
>                 Key: HBASE-12928
>                 URL: https://issues.apache.org/jira/browse/HBASE-12928
>             Project: HBase
>          Issue Type: Improvement
>          Components: Balancer
>    Affects Versions: 0.99.2
>            Reporter: Jianwei Cui
>            Priority: Minor
>
> BaseLoadBalancer#needsBalance will be invoked to judge whether needs to do balancing. StochasticLoadBalancer do balancing by considering region count skew cost, read/write request cost, locality cost, etc. However, it seems that only sloppiness of region count is checked in BaseLoadBalancer#needsBalance, there may be cases that request/locality cost is high when region count is even, this will skip the actual balancing so that can't achieve lower cost. There, Do we need to check sloppiness of other factors(read/write request, locality, etc) in needsBalance?



--
This message was sent by Atlassian Jira
(v8.20.7#820007)