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

Yield call into storage engine after releasing global lock

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Storage Execution
    • ALL

      Query yield call saveLockStateAndUnlock which returns true if locks were released. If locks were released we proceed to check for interrupt and finally abandoning the WT snapshot.

      It is not safe to call into the storage engine without a global lock. There could for example be a shutdown in progress that has acquired the global lock in MODE_X and is shutting down the storage engine. If this is the case, we may throw when checking for interrupt which again causes the snapshot do be abandoned when the GlobalLock type is destroyed.

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            henrik.edin@mongodb.com Henrik Edin
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: