-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution NAMER
-
Fully Compatible
-
Execution Team 2023-03-06, Execution Team 2023-04-03, Execution Team 2023-05-01, Execution Team 2023-05-29, Execution Team 2023-06-12, Execution NAMR Team 2023-09-04, Execution NAMR Team 2023-09-18
In dbtests.cpp, we upgrade a collection level IX lock to an X lock: https://github.com/10gen/mongo/blob/9b9a63ba1119f69154b360b2758091b64e0310ce/src/mongo/dbtests/dbtests.cpp#L181-L195
Simple fix would be to take the X lock right away but we can also potentially drop the IX lock on the collection before taking the X lock? Either way, if we acquire the IX lock for the collection and go to drop the collection, we would be upgrading the lock so we need to address that.
- is depended on by
-
SERVER-73040 Ban all lock upgrades
- Closed