Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-42947

LockerImpl::saveLockStateAndUnlock should cleanup the check that's used to skip the resources that never have to be saved and restored.

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.3.1
    • None
    • None
    • None
    • Fully Compatible
    • Repl 2019-08-26, Repl 2019-09-09

    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.

      Attachments

        Activity

          People

            suganthi.mani@mongodb.com Suganthi Mani
            suganthi.mani@mongodb.com Suganthi Mani
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: