Make add/remove shard hook resilient to jstestfuzz setting setDefaultRWConcern

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • v8.3
    • CAR Team 2026-04-27
    • 0
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      The jstestfuzz may set an invalid default RW concern, which causes the add/remove shard hook to fail.

      The FuzzerRestoreSettings hook resets the default RW concern before hooks run, but that only applies to non-background hooks.

      Find a way to make the background add/remove shard hook resilient. Perhaps by retrying the UnsatisfiableWriteConcern error or maybe specifying the write concern explicitly.

            Assignee:
            Wolfee Farkas
            Reporter:
            Yujin Kang Park
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: