Details
-
Test
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
3.0.0-alpha-1, 2.0.0
-
None
-
Reviewed
Description
Some test ordering issues were exposed by adding new tests in HBASE-22349. I think this is a legitimate issue which is tracked in HBASE-26988.
But we can update the tests to be consistent in how they update configuration to reduce confusion, removing the unset calls.
We can also update other configuration values to significantly speed up the long-running methods. Methods that are simply checking for balancer plans do not need to runMaxSteps. All we need to do is run enough steps to guarantee we will plan to move one region. That can be far fewer than the tens of millions of steps we may be running given runMaxSteps.
Attachments
Issue Links
- Discovered while testing
-
HBASE-22349 Stochastic Load Balancer skips balancing when node is replaced in cluster
- Resolved
- relates to
-
HBASE-26988 Balancer should reset to default setting for hbase.master.loadbalance.bytable if dynamically reloading configuration
- Resolved
- links to