Uploaded image for project: 'Kudu'
  1. Kudu
  2. KUDU-2551

TsRecoveryITest.TestTabletRecoveryAfterSegmentDelete is a bit flaky

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 1.8.0
    • 1.9.0
    • test
    • None

    Description

      The TsRecoveryITest.TestTabletRecoveryAfterSegmentDelete test is flaky in TSAN builds, but the error is not about thread race. Probably, increasing timeout for waiting for the assertion would help:

      kudu/src/kudu/integration-tests/ts_recovery-itest.cc:185
Failed
Bad status: Timed out: Timed out waiting for number of WAL segments on tablet d447fbb147024bad80475ff998cb87ab on TS 0 to be 4. Found 3

      Attachments

        Activity

          People

            awong Andrew Wong
            aserbin Alexey Serbin
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: