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

Hudson commented on HBASE-29262:
--------------------------------

Results for branch branch-3
        [build #406 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/406/]: 
(x) *{color:red}-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/branch-3/406/General_20Nightly_20Build_20Report/]








(x) {color:red}-1 jdk17 hadoop3 checks{color}
-- Something went wrong running this stage, please [check relevant console 
output|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/406//console].


(/) {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%20Nightly/job/branch-3/406/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]






(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test for 3.3.5 {color}
(/) {color:green}+1 client integration test for 3.3.6 {color}
(/) {color:green}+1 client integration test for 3.4.0 {color}
(/) {color:green}+1 client integration test for 3.4.1 {color}


> StochasticLoadBalancer should use the CostFunction epsilon when evaluating 
> whether a move improved costs
> --------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-29262
>                 URL: https://issues.apache.org/jira/browse/HBASE-29262
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Ray Mattingly
>            Assignee: Ray Mattingly
>            Priority: Major
>              Labels: pull-request-available
>
> StochasticLoadBalancer should use the CostFunction epsilon when evaluating 
> whether a move improved costs. Right now the balancer might make superfluous 
> / low-value moves due to floating-point imprecision.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to