[ 
https://issues.apache.org/jira/browse/HBASE-30093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18145441#comment-18145441
 ] 

Hudson commented on HBASE-30093:
--------------------------------

Results for branch branch-3
        [build #135 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase-Backwards-Compatibility-Test/job/branch-3/135/]:
 (x) *{color:red}-1 overall{color}*
----
Backwards compatibility checks:
(/) {color:green}+1 jdk17 hadoop 3.3.5 backward compatibility checks{color}
-- For more information [see jdk17 
report|https://ci-hbase.apache.org/job/HBase-Backwards-Compatibility-Test/job/branch-3/135/console]


(x) {color:red}-1 jdk17 hadoop 3.3.6 backward compatibility checks{color}
-- For more information [see jdk17 
report|https://ci-hbase.apache.org/job/HBase-Backwards-Compatibility-Test/job/branch-3/135/console]


(/) {color:green}+1 jdk17 hadoop 3.4.0 backward compatibility checks{color}
-- For more information [see jdk17 
report|https://ci-hbase.apache.org/job/HBase-Backwards-Compatibility-Test/job/branch-3/135/console]


(/) {color:green}+1 jdk17 hadoop 3.4.1 backward compatibility checks{color}
-- For more information [see jdk17 
report|https://ci-hbase.apache.org/job/HBase-Backwards-Compatibility-Test/job/branch-3/135/console]


(/) {color:green}+1 jdk17 hadoop 3.4.2 backward compatibility checks{color}
-- For more information [see jdk17 
report|https://ci-hbase.apache.org/job/HBase-Backwards-Compatibility-Test/job/branch-3/135/console]


> LoadBalancer related tests timed out
> ------------------------------------
>
>                 Key: HBASE-30093
>                 URL: https://issues.apache.org/jira/browse/HBASE-30093
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Balancer, test
>            Reporter: Duo Zhang
>            Assignee: mazhengxuan
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.0.0-alpha-1, 2.7.0, 3.1.0, 3.0.1, 2.6.8, 2.5.17
>
>
> Sonnet 4.5(4.6?) summary
> TestStochasticLoadBalancerRegionReplicaSameHosts
> Root cause
> StochasticLoadBalancer.balanceTable() set 
> cluster.setStopRequestedAt(startTime + maxRunningTime) at the very beginning 
> of the method, before build ing costs (initCosts), the first computeCost, 
> needsBalance, and other setup.
> So the entire maxRunningTime budget (e.g. 250 ms in 
> StochasticBalancerTestBase) was counting initialization + search, not just 
> the stochastic walk.
> On a slow or busy CI host, setup alone could take ~250 ms or more. Then when 
> the walk started, isStopRequested() was already true (or became true af ter a 
> single rejected move). The loop could exit with step still 0, no accepted 
> moves, and balanceCluster returning null even though region repl icas were 
> still colocated on the same host—so 
> TestStochasticLoadBalancerRegionReplicaSameHosts failed. Locally, setup is 
> usually only tens of ms, so the bug rarely shows up.
> Fix
> Set setStopRequestedAt only after initialization is done, immediately before 
> the stochastic for loop, using a new timestamp (searchStartTime + 
> maxRunningTime). That way maxRunningTime applies to the search phase only, 
> which matches the intended meaning of the limit and avoids “no search time 
> left” on loaded agents.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to