[SERVER-46703] Make a variant of checkShardVersionOrThrow which doesn't treat UNKNOWN shard version as UNSHARDED Created: 09/Mar/20  Updated: 29/Oct/23  Resolved: 10/Apr/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Task Priority: Major - P3
Reporter: Marcos José Grillo Ramirez Assignee: Kaloian Manassiev
Resolution: Fixed Votes: 0
Labels: PM-1645-Milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-46981 The MongoS write commands scheduler d... Closed
depends on SERVER-46593 Remove locks from ShardServerProcessI... Closed
is depended on by SERVER-32198 Missing collection metadata on the sh... Closed
Related
related to SERVER-47492 Complete TODO listed in SERVER-46703 Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-03-23, Sharding 2020-04-06, Sharding 2020-04-20
Participants:

 Description   

As part of the Make Migration Commit Protocol Robust project, we want to make sure that every function on the CollectionShardingState API do not allow unintended usage if the collection metadata is unknown



 Comments   
Comment by Githook User [ 10/Apr/20 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-46703 Make `checkShardVersionOrThrow` throw SSV if the metadata is not known

Introduces a checkShardVersionOKOrThrow_DEPRECATED variant so that we can incrementally fix the places, which are not prepared to catch StaleConfig exceptions.
Branch: master
https://github.com/mongodb/mongo/commit/7645ff98bb0f289f8eb1605cb743b414e5ded0fc

Generated at Thu Feb 08 05:12:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.