Account for errors caused by removeShard in add/remove shard suites

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • ALL
    • CAR Team 2025-06-23
    • 0
    • None
    • 3
    • TBD
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      A number of suites that run add/remove shard in the background were added recently, which can conflict with tests that run operations that target a specific shard, like moveChunk and movePrimary. We should make sure any tests that run in these suites account for errors that can happen due to concurrent add/remove shards.

      This ticket came out of an issue seen specifically with fsm_workloads/crud/move_primary_with_crud.js needing to account for ShardNotFound when running movePrimary, but it might worth auditing whether there are any other tests that need to add similar accounting, so filed a more general ticket.

            Assignee:
            Allison Easton
            Reporter:
            Janna Golden
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: