You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/05/02 17:35:00 UTC
[jira] [Updated] (HBASE-26989) TestStochasticLoadBalancer has some slow methods, and inconsistent set, reset, unset of configuration
[ https://issues.apache.org/jira/browse/HBASE-26989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Kyle Purtell updated HBASE-26989:
----------------------------------------
Fix Version/s: 2.5.0
3.0.0-alpha-3
2.4.13
Status: Patch Available (was: Open)
> TestStochasticLoadBalancer has some slow methods, and inconsistent set, reset, unset of configuration
> -----------------------------------------------------------------------------------------------------
>
> Key: HBASE-26989
> URL: https://issues.apache.org/jira/browse/HBASE-26989
> Project: HBase
> Issue Type: Test
> Components: Balancer, test
> Affects Versions: 2.0.0, 3.0.0-alpha-1
> Reporter: David Manning
> Assignee: David Manning
> Priority: Minor
> Fix For: 2.5.0, 3.0.0-alpha-3, 2.4.13
>
>
> 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}}.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)