[
https://issues.apache.org/jira/browse/HBASE-26989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17531374#comment-17531374
]
Hudson commented on HBASE-26989:
--------------------------------
Results for branch master
[build #578 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/578/]:
(/) *{color:green}+1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/578/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/578/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/578/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> 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: 3.0.0-alpha-1, 2.0.0
> Reporter: David Manning
> Assignee: David Manning
> Priority: Minor
> Fix For: 2.5.0, 3.0.0-alpha-3
>
>
> 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)
