[SERVER-74083] Implement chunk checks in checkConsistencyMetadata command Created: 16/Feb/23  Updated: 29/Oct/23  Resolved: 31/Mar/23

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

Type: Task Priority: Major - P3
Reporter: Pol Pinol Assignee: Pol Pinol
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-74246 Extend metadata_consistency_util_test... Closed
Gantt Dependency
has to be done before SERVER-75490 Use kSnapshotReadConcern when getting... Closed
has to be done before SERVER-74246 Extend metadata_consistency_util_test... Closed
has to be done before SERVER-75432 Implement history chunk checks in che... Closed
Issue split
split from SERVER-73187 Implement chunks and zones checks in ... Closed
Problem/Incident
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-02-20, Sharding EMEA 2023-03-06, Sharding EMEA 2023-03-20, Sharding EMEA 2023-04-03
Participants:
Linked BF Score: 162

 Description   

DB primary shard send _configsvrCheckMetadataConsistency(dbName) to the config server to check chunks 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


 Comments   
Comment by Githook User [ 31/Mar/23 ]

Author:

{'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}

Message: SERVER-74083 Implement chunk checks in checkConsistencyMetadata command
Branch: master
https://github.com/mongodb/mongo/commit/0551b18ead895bf75d4093c63cb1b167feeafa19

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