|
DB primary shard send _configsvrCheckMetadataConsistency(dbName) to the config server to check the routing table consistency:
- There should be no chunk with empty history.
- The shard name in the first element of the history array matches the shard name in the top level of the chunk (code).
- No range gaps - Chunks must always cover the entire shard key space for a specific collection [minKey, maxKey)
- No overlap ranges for chunks or tags
No spare chunks - No leftover chunks from deleted collections (only available on cluster-level check) (not done in this ticket)
|