[SERVER-75456] establishConsistentCollection concurrent with rename with dropTarget=true may return nullptr Created: 29/Mar/23  Updated: 29/Oct/23  Resolved: 03/Apr/23

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

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

Issue Links:
Depends
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2023-04-17
Participants:
Linked BF Score: 14

 Description   

If the namespace is under pending commit but the commit has not been performed with the storage engine yet we will use the catalogId from the pending commit and discover that the namespace doesn't match and return nullptr.



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

Author:

{'name': 'Henrik Edin', 'email': 'henrik.edin@mongodb.com', 'username': 'henrikedin'}

Message: SERVER-75456 Fix establishConsistentCollection when used concurrently with rename with dropTarget=true
Branch: master
https://github.com/mongodb/mongo/commit/1cace66e813b95207985fb612bfcbb99dd733878

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