You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Viraj Jasani (Jira)" <ji...@apache.org> on 2020/08/18 03:04:00 UTC
[jira] [Comment Edited] (HBASE-24894) [Flakey Test]
TestStochasticLoadBalancer.testMoveCostMultiplier
[ https://issues.apache.org/jira/browse/HBASE-24894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17179320#comment-17179320 ]
Viraj Jasani edited comment on HBASE-24894 at 8/18/20, 3:03 AM:
----------------------------------------------------------------
[~filtertip] FYI. I have also experienced this very recently. Seems something to do with offpeak hours config and test might stay flaky for a particular duration consistently?
was (Author: vjasani):
[~filtertip] FYI. I have also experienced this very recently.
> [Flakey Test] TestStochasticLoadBalancer.testMoveCostMultiplier
> ---------------------------------------------------------------
>
> Key: HBASE-24894
> URL: https://issues.apache.org/jira/browse/HBASE-24894
> Project: HBase
> Issue Type: Test
> Components: Balancer, master, test
> Affects Versions: 3.0.0-alpha-1, 2.3.0
> Reporter: Nick Dimiduk
> Priority: Major
>
> I've noticed this test has gotten flakey on a couple PRs. The only recent change to the class under test is HBASE-24709.
> Failure looks like:
> {noformat}
> [ERROR] Failures:
> [ERROR] org.apache.hadoop.hbase.master.balancer.TestStochasticLoadBalancer.testMoveCostMultiplier
> [ERROR] Run 1: TestStochasticLoadBalancer.testMoveCostMultiplier:304 expected:<3.0> but was:<7.0>
> [ERROR] Run 2: TestStochasticLoadBalancer.testMoveCostMultiplier:304 expected:<3.0> but was:<7.0>
> [ERROR] Run 3: TestStochasticLoadBalancer.testMoveCostMultiplier:304 expected:<3.0> but was:<7.0>
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)