Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-73187

Implement chunks and zones checks in checkConsistencyMetadata command

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Sharding EMEA
    • Sharding EMEA 2023-01-23, Sharding EMEA 2023-02-06

      DB primary shard send _configsvrCheckMetadataConsistency(dbName) to the config server to check the routing table consistency:

      1. There should be no chunk with empty history.
      2. The shard name in the first element of the history array matches the shard name in the top level of the chunk (code). 
      3. No range gaps -  Chunks must always cover the entire shard key space for a specific collection [minKey, maxKey)
      4. No overlap ranges for chunks or tags
      5. No spare chunks - No leftover chunks from deleted collections (only available on cluster-level check) (not done in this ticket)

            Assignee:
            backlog-server-sharding-emea [DO NOT USE] Backlog - Sharding EMEA
            Reporter:
            pol.pinol@mongodb.com Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: