[jira] [Updated] (KUDU-3559) AutoRebalancerTest.TestMaxMovesPerServer is flaky

["Marton Greber (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KUDU-3559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marton Greber updated KUDU-3559:
--------------------------------
        Parent: KUDU-3578
    Issue Type: Sub-task  (was: Bug)

> AutoRebalancerTest.TestMaxMovesPerServer is flaky
> -------------------------------------------------
>
>                 Key: KUDU-3559
>                 URL: https://issues.apache.org/jira/browse/KUDU-3559
>             Project: Kudu
>          Issue Type: Sub-task
>          Components: test
>    Affects Versions: 1.17.0
>            Reporter: Alexey Serbin
>            Priority: Major
>         Attachments: auto_rebalancer-test.log.xz
>
>
> The {{AutoRebalancerTest.TestMaxMovesPerServer}} is flaky, sometimes failing with an error like below.  The full log is attached.
> {noformat}
> src/kudu/master/auto_rebalancer-test.cc:196: Failure
> Expected equality of these values:
>   0
>   NumMovesScheduled(leader_idx, BalanceThreadType::LEADER_REBALANCE)
>     Which is: 1
> src/kudu/util/test_util.cc:395: Failure
> Failed
> Timed out waiting for assertion to pass.
> src/kudu/master/auto_rebalancer-test.cc:575: Failure
> Expected: CheckNoLeaderMovesScheduled() doesn't generate new fatal failures in the current thread.
>   Actual: it does.
> {noformat}



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