[SERVER-42947] LockerImpl::saveLockStateAndUnlock should cleanup the check that's used to skip the resources that never have to be saved and restored. Created: 21/Aug/19  Updated: 29/Oct/23  Resolved: 23/Aug/19

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

Type: Task Priority: Major - P3
Reporter: Suganthi Mani Assignee: Suganthi Mani
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Repl 2019-08-26, Repl 2019-09-09
Participants:

 Description   

In LockerImpl::saveLockStateAndUnlock, we check the resource locks that needs to be skipped from saving and restoring. This check no longer make sense after SERVER-39860. This line was mainly introduced to handle PBWM locks and we handle/release the global lock over here. As a part of unlocking, we also remove the global lock request from LockerImpl::_request list. So, it's impossible for LockerImpl::_request list to contain RESOURCE_GLOBAL/global lock request) over here. To be noted, after SERVER-39860, PBWM locks are no longer considered as RESOURCE_GLOBAL.



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

Author:

{'name': 'Suganthi Mani', 'email': 'suganthi.mani@mongodb.com', 'username': 'smani87'}

Message: SERVER-42947 LockerImpl::saveLockStateAndUnlock should no longer check
for global resource request for skipping the resources that never have to be saved and restored.
Branch: master
https://github.com/mongodb/mongo/commit/1d21a5b64114fe777ee879713552048c0fbba631

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