Details
-
Task
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
None
-
Fully Compatible
-
Sharding EMEA 2023-05-01, Sharding EMEA 2023-05-15
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.
Attachments
Issue Links
- related to
-
SERVER-76488 Make CheckMetadataConsistency check db and shard version
-
- Blocked
-