Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 7.0.0-rc0
Affects Version/s: None
Component/s: None
Labels:
None

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
Linked BF Score:
162
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

has to be done before

SERVER-75490 Use kSnapshotReadConcern when getting chunks from config server at checkMetadataConsistency

Closed

SERVER-74246 Extend metadata_consistency_util_test.cpp to test randomly generated routing tables for chunks inconsistencies

Closed

SERVER-75432 Implement history chunk checks in checkConsistencyMetadata cmd

Closed

is depended on by

SERVER-74246 Extend metadata_consistency_util_test.cpp to test randomly generated routing tables for chunks inconsistencies

Closed

split from

SERVER-73187 Implement chunks and zones checks in checkConsistencyMetadata command

Closed

Assignee:: Pol Pinol
Reporter:: Pol Pinol
Participants:: Githook User, Pol Pinol
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Feb 16 2023 10:50:00 AM UTC
Updated:: Oct 29 2023 09:26:11 PM UTC
Resolved:: Mar 31 2023 11:38:14 AM UTC
Confidence Status Last Update:: 20/Feb/23 9:05 AM