[SERVER-33043] Only setFCV should take the fcvLock (ResourceMutex) in exclusive mode Created: 31/Jan/18  Updated: 29/Oct/23  Resolved: 13/Feb/18

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: 3.7.1
Fix Version/s: 3.7.3

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (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-33044 Move the fcvLock from being held for ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage 2018-02-26
Participants:

 Description   

Also, all acquisitions of the fcvLock must invariant that !opCtx->lockState()->isLocked() before taking the lock, regardless of the mode. This is because the usage expectations around fcvLock is that it will always be taken before global/database/collection locks. This is to avoid deadlocks.



 Comments   
Comment by Githook User [ 13/Feb/18 ]

Author:

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

Message: SERVER-33043 Only setFCV should take the fcvLock (ResourceMutex) in exclusive mode
Branch: master
https://github.com/mongodb/mongo/commit/d3b53c3acae86649f56b44c47258b38e76023457

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