[SERVER-73187] Implement chunks and zones checks in checkConsistencyMetadata command Created: 23/Jan/23  Updated: 28/Mar/23  Resolved: 28/Mar/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Pol Pinol Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Gantt Dependency
has to be done after SERVER-74034 Add config server database level chec... Closed
Issue split
split to SERVER-74083 Implement chunk checks in checkConsis... Closed
split to SERVER-74084 Implement zones checks in checkConsis... Closed
Assigned Teams:
Sharding EMEA
Sprint: Sharding EMEA 2023-01-23, Sharding EMEA 2023-02-06
Participants:

 Description   

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)

Generated at Thu Feb 08 06:23:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.