[SERVER-62194] Add multiple collection locking capability to AutoGetCollection Created: 20/Dec/21  Updated: 29/Oct/23  Resolved: 14/Jan/22

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

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-59958 Extend multi-collection locking to th... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2021-12-27, Execution Team 2022-01-10, Execution Team 2022-01-24
Participants:

 Description   

E.g. AutoGetCollection internally uses the new AutoGetCollectionMulti class created inĀ SERVER-59958

UPDATE:
Use the existing algorithm to sort lock order by lock ResourceId. (query yield restoration of locks re-acquires in a certain order).



 Comments   
Comment by Githook User [ 12/Jan/22 ]

Author:

{'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@mongodb.com', 'username': 'DiannaHohensee'}

Message: SERVER-62194 Make AutoGetCollection accept multiple namespaces to lock.
Branch: master
https://github.com/mongodb/mongo/commit/42c4a1e81df86cd3b808bb982b62f527c0de71d8

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