[SERVER-75643] Not all paths of AutoGetCollectionForReadLockFreePITCatalog check for DBVersion Created: 04/Apr/23  Updated: 29/Oct/23  Resolved: 05/Apr/23

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

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-74816 Unnecessary call to `checkOnPrimarySh... Closed
Related
is related to SERVER-75634 The logic in attachCursorSourceToPipe... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding EMEA 2023-04-17
Participants:

 Description   

The non-suboperation path of AutoGetCollectionForReadLockFreePITCatalog performs DBVersion check after it has already attempted to resolve a UUID into a Namespace. This means that operations, which target unsharded collections by UUID, such as internal local reads in query, will hit the NamespaceNotFound error before the DBVersion mismatch one and won't get a chance to retarget.



 Comments   
Comment by Githook User [ 05/Apr/23 ]

Author:

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

Message: SERVER-75643 Check for DBVersion in all paths of AutoGetCollectionForReadLockFreePITCatalog
Branch: master
https://github.com/mongodb/mongo/commit/ecabedb84d3e5a22c198582917eb6c0d5dd9f8df

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