[SERVER-64464] Check the shard version for collections when AutoGetCollection is instantiated Created: 14/Mar/22  Updated: 29/Oct/23  Resolved: 30/Mar/22

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

Type: Task Priority: Major - P3
Reporter: Antonio Fuschetto Assignee: Antonio Fuschetto
Resolution: Fixed Votes: 0
Labels: PM-2144-Milestone-0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-64630 Use the received shard version to avo... Closed
depends on SERVER-64468 Delete SucceedsIfFilteringMetadataUUI... Closed
Problem/Incident
causes SERVER-65208 Check the top-chunk before refreshing... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2022-03-21, Sharding EMEA 2022-04-04
Participants:
Linked BF Score: 166

 Description   

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.



 Comments   
Comment by Antonio Fuschetto [ 30/Mar/22 ]

Author:

{'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}

Message: SERVER-64464 Check the shard version for collections when AutoGetCollection is instantiated
Branch: master
https://github.com/mongodb/mongo/commit/622b08bf511c9a632494aafcd44c7290fbda7d04

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