[SERVER-61609] Determine if global lock upgrade is necessary in ReplicationCoordinatorExternalStateImpl::_dropAllTempCollections Created: 18/Nov/21  Updated: 29/Oct/23  Resolved: 01/Jun/22

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

Type: Task Priority: Major - P3
Reporter: Dan Larkin-York Assignee: Haley Connelly
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-60621 Investigate if we can ban upgrading t... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-06-13
Participants:

 Description   

Currently this method explicitly holds the global lock in IS mode, then takes DB locks in IX mode, triggering an upgrade. We'd like to avoid upgrading the global lock if possible.



 Comments   
Comment by Githook User [ 01/Jun/22 ]

Author:

{'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}

Message: SERVER-61609 Prevent lock upgrade in ReplicationCoordinatorExternalStateImpl::_dropAllTempCollections
Branch: master
https://github.com/mongodb/mongo/commit/62203e9533de80616e0830ea90b6940796c38888

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