Uploaded image for project: 'Kudu'
  1. Kudu
  2. KUDU-3578 De-flaking effort
  3. KUDU-3559

AutoRebalancerTest.TestMaxMovesPerServer is flaky

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 1.17.0
    • None
    • test
    • None

    Description

      The AutoRebalancerTest.TestMaxMovesPerServer is flaky, sometimes failing with an error like below. The full log is attached.

      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.
      

      Attachments

        1. auto_rebalancer-test.log.xz
          44 kB
          Alexey Serbin

        Activity

          People

            Unassigned Unassigned
            aserbin Alexey Serbin
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: