[SERVER-78765] RoutingTableConsistencyChecker and CheckMetadataConsistency must account for tracked unsharded collections Created: 07/Jul/23  Updated: 29/Oct/23  Resolved: 19/Sep/23

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

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Enrico Golfieri
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-78755 Add an optional<bool> `unsplittable` ... Closed
depends on SERVER-78756 Filter out `unsplittable` field on ba... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-07-24, Sharding EMEA 2023-08-07, Sharding EMEA 2023-08-21, Sharding EMEA 2023-09-04, Sharding EMEA 2023-09-18, Sharding EMEA 2023-10-02
Participants:

 Description   

Both the RoutingTableConsistencyChecker hook and the ConfigsvrCheckMetadataConsistencyCommand must check that if an entry in config.collections is labeled as unsplittable then it must always only have 1 chunk.



 Comments   
Comment by Githook User [ 18/Sep/23 ]

Author:

{'name': 'egol', 'email': 'enrico.golfieri@mongodb.com', 'username': 'enricogolfieri'}

Message: SERVER-78765 extend CheckMetadataConsistency to include unsplittable collections
Branch: master
https://github.com/mongodb/mongo/commit/2fed04292b5e5794eb71f1af9953922d14643535

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