-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Labels:None
-
Fully Compatible
-
Repl 2019-08-26, Repl 2019-09-09
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.