[SERVER-76609] Convert tassert in CheckMetadataConsistency into a proper inconsistency Created: 27/Apr/23  Updated: 29/Oct/23  Resolved: 09/May/23

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

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

Issue Links:
Related
related to SERVER-76488 Make CheckMetadataConsistency check d... Blocked
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-05-01, Sharding EMEA 2023-05-15
Participants:

 Description   

Originally we added this tassert that is triggered when a shard has a collection marked as UNSHARDED in its CollectionShardingState while instead is actually sharded.

We discovered that due to the bug described in SERVER-76489, this can actually happen, and it will bring to data-loss scenarios. Thus, I believe that we should report this as an inconsistency rather than failing the entire CheckMetadataConsistency command.



 Comments   
Comment by Githook User [ 08/May/23 ]

Author:

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

Message: SERVER-76609 Convert tassert in CheckMetadataConsistency into a proper inconsistency
Branch: master
https://github.com/mongodb/mongo/commit/5edc5dc5edccd876c74dc641809b7cc831acf764

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