Details
-
Task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Ran into a customer case where the StochasticLoadBalancer was consistently deciding not to balance when bringing new region servers on line. Even setting the class to TRACE logging would only log a summary statement like:
2020-04-03 00:29:55,133 TRACE org.apache.hadoop.hbase.master.balancer.StochasticLoadBalancer: Skipping load balancing because balanced cluster; total cost is 25.24853189705185, sum multiplier is 602.0 min cost which need balance is 0.05
Without any details about what went into that decision it's really hard to figure out what we need to tune to get the behavior we want.
Attachments
Issue Links
- links to