Extend checkMetadataConsistency to detect CSR states without a matching durable entry

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: 9.0.0-rc0, 9.1.0-rc0
    • Component/s: Sharding
    • Catalog and Routing
    • CAR Team 2026-08-03
    • 🟦 Shard Catalog
    • None
    • None
    • None
    • None
    • None
    • None

      Ensure CMC and/or our testing infra can catch the class of issues discovered by:

      • SERVER-132477 movePrimary does not clear CSR state for untracked collections
      • SERVER-131968 Invalidate metadata on secondaries during removeShard coordinator

       

      It seems the main gap is that we don't cover all cases where a CSR state is no longer supported by the durable authoritative state.

            Assignee:
            Joan Bruguera Micó
            Reporter:
            Joan Bruguera Micó
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: