Determine if we can avoid global lock upgrade in dbtest StorageTimestampTest

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Execution Team 2022-05-30
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

        1. backtrace.log
          46 kB

            Assignee:
            Yujin Kang Park
            Reporter:
            Dan Larkin-York
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: