CheckMetadataConsistency looks for orphan entries in config.shard.catalog.collections and chunks

XMLWordPrintableJSON

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

      checkMetadataConsistency should check for orphan entries in the shard catalog.

      An orphan entry can be:

      • The collection is UNTRACKED* (doesn't exist on the global catalog), but there is one entry in config.shard.catalog.collections.
      • The collection is UNTRACKED* (doesn't exist on the global catalog), but there are chunk entries in config.shard.catalog.chunks.
      • The collection is TRACKED (exists in global catalog), and a shard owning no chunks has entries in config.shard.catalog.chunks (we need to filter out entries that remained for history field).

      Scenarios where entries are acceptable:

      • The collection is TRACKED and a shard owning no chunks has one entry in config.shard.catalog.collections.
      • The collection is TRACKED and a shard owning no chunks has NO entry in config.shard.catalog.collections.

       

      *Note: UNTRACKED here means unsharded collection living on the DB primary shard or literally leftovers and the collection doesn't exist.

            Assignee:
            Rustam Gusein-zade
            Reporter:
            Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: