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

Determine if we can avoid global lock upgrade in dbtest StorageTimestampTest

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 6.1.0-rc0
    • None
    • None
    • Fully Compatible
    • Execution Team 2022-05-30

    Description

      Currently in SecondaryInsertTimes::run(), we take the global lock in IX mode via AutoGetCollection, then later in applyOps, we upgrade the global lock to X mode via Lock::GlobalWrite. Given that it's just the test construct, this probably isn't a real problem, but we are working to ban upgrading the global lock in SERVER-60621, and this test fails as a result.

      Attachments

        Issue Links

          is depended on by

          Task - A task that needs to be done. SERVER-60621 Investigate if we can ban upgrading the global lock

          • Major - P3 - Major loss of function.
          • In Progress
          related to

          Task - A task that needs to be done. SERVER-66609 Avoid global lock upgrade in storage_timestamp_test.cpp

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

          Activity

            People

              yujin.kang@mongodb.com Yujin Kang Park
              dan.larkin-york@mongodb.com Dan Larkin-York
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: