checkMetadataConsistency should check the DBPrimary's shard catalog for a sharded collection even if it doesn't own any chunks

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • CAR Team 2026-05-11, CAR Team 2026-05-25, CAR Team 2026-06-08
    • 🟦 Shard Catalog
    • None
    • None
    • None
    • None
    • None
    • None

      In an authoritative world, it’s important to check the DBPrimary shards for tracked collections even if they don’t own any chunks. DBPrimary shards must always contain a chunk entry for all of their collections; when a shard doesn’t own chunks for a given collection, it instead stores a chunkless placeholder entry.

            Assignee:
            Rustam Gusein-zade
            Reporter:
            Silvia Surroca
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: