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

Yield call into storage engine after releasing global lock

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Duplicate
    • None
    • None
    • None
    • None
    • Storage Execution
    • ALL

    Description

      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.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. SERVER-70338 Query yield accesses the storage engine without locks

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-55173 Segmentation fault in WiredTigerSession::releaseCursor

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-60335 Wait for all user operations to be killed before executing WT Rollback To Stable

          • Major - P3 - Major loss of function.
          • Backlog

          Activity

            People

              backlog-server-execution Backlog - Storage Execution Team
              henrik.edin@mongodb.com Henrik Edin
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: