-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
Sharding EMEA 2022-03-21, Sharding EMEA 2022-04-04
-
166
As a prerequisite to push the CollectionShardingState to the Storage Catalog, when the collection locks are acquired (AutoGetCollection class), the shard version attached to the operation context must be consistent with the information stored in the local metadata.
The goal of this task is to validate the shard version (checkShardVersionOrThrow) when the passed namespace corresponds to a collection in the local catalog.
- causes
-
SERVER-65208 Check the top-chunk before refreshing the local metadata
- Closed
- depends on
-
SERVER-64630 Use the received shard version to avoid unnecessary refresh of the catalog cache
- Closed
-
SERVER-64468 Delete SucceedsIfFilteringMetadataUUIDInitiallyDifferentFromTaskUUIDButMatchesAfterRefresh
- Closed