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

Investigate if we can ban upgrading the global lock

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 6.3.0-rc0
    • None
    • None
    • Storage Execution
    • Fully Compatible
    • Execution Team 2023-02-20, Execution Team 2023-02-06
    • 169

    Description

      Upgrading the global lock mode without first releasing the lock held can have bad side effects (namely deadlock and resource exhaustion). We've removed some cases where this can happen (most recently in SERVER-59219). We think we can explicitly ban this behavior in code, as it could help us identify additional bugs we haven't hit yet, and avoid future ones. That said, there are some instances where we currently upgrade the global lock, and we'll need to fix these first.

      Attachments

        Issue Links

          depends on

          Task - A task that needs to be done. SERVER-61601 Determine if global lock upgrade is necessary when implicitly creating collection during createIndexes

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

          Task - A task that needs to be done. SERVER-61609 Determine if global lock upgrade is necessary in ReplicationCoordinatorExternalStateImpl::_dropAllTempCollections

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

          Task - A task that needs to be done. SERVER-61733 Determine if global lock upgrade is necessary in transaction_participant.cpp:fetchActiveTransactionHistory

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

          Task - A task that needs to be done. SERVER-61786 Determine if we can avoid global lock upgrade in IndexBuildsCoordinatorMongod::setCommitQuorum

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

          Task - A task that needs to be done. SERVER-61788 Determine if we can avoid global lock upgrade in dbtest StorageTimestampTest

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

          Task - A task that needs to be done. SERVER-61789 Determine if we can avoid global lock upgrade in dbtests/repltests.cpp

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

          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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-67695 Remove the write-blocking mode of dbCheck

          • Major - P3 - Major loss of function.
          • Closed
          is depended on by

          Task - A task that needs to be done. SERVER-73040 Investigate if we can ban all lock upgrades

          • Major - P3 - Major loss of function.
          • Blocked
          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-66145 Identify and fix locations that write while holding read tickets

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-66719 dbCheck FCV lock upgrade causes deadlock with setFCV

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

          Activity

            People

              fausto.leyva@mongodb.com Fausto Leyva
              dan.larkin-york@mongodb.com Dan Larkin-York
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: