[SERVER-80428] Avoid lock upgrade when renaming collection for apply ops Created: 25/Aug/23  Updated: 29/Oct/23  Resolved: 25/Aug/23

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

Type: Improvement Priority: Major - P3
Reporter: Gregory Noma Assignee: Gregory Noma
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-73040 Ban all lock upgrades Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution NAMR Team 2023-09-04
Participants:

 Description   

When renaming a collection for apply ops, we take database and collection IS locks but then later we take a database X lock which results in a lock upgrade.



 Comments   
Comment by Githook User [ 25/Aug/23 ]

Author:

{'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}

Message: SERVER-80428 Avoid lock upgrade when renaming collection for apply ops
Branch: master
https://github.com/mongodb/mongo/commit/378e80c53da30bfabe4716e8a974d15b1284a8ae

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