Be more permissive with moveChunk failures in FSM tests when running under TSAN

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0, 8.0.0-rc11
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • v8.0
    • Cluster Scalability 2024-07-08
    • 200
    • 1
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In FSM tests, we allow errors that come from specific steps of the moveChunk command to retry if we're running with stepdowns. We should also allow this if we're running on TSAN, since this slows down the workload. It will be even more precise if we check the error message for timeout-related messages, so as to not paper over real bugs.

      We can check if we're running on TSAN from jstests like so.

              Assignee:
              Jack Mulrow
              Reporter:
              Blake Oler
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: