Details
Description
Currently when numMaxRegionsPerTable of a given table increases above the current maximum, the value is not properly updated. This means that the cost for Table Skew cannot get worse for a given region move during the balancer process leading to an imbalanced cluster with respect to Table Skew.
Attachments
Attachments
Issue Links
- relates to
-
HBASE-18480 The cost of BaseLoadBalancer.cluster is changed even if the rollback is done
- Resolved