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

Determine if global lock upgrade is necessary in transaction_participant.cpp:fetchActiveTransactionHistory

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 6.1.0-rc0
    • None
    • None
    • Fully Compatible
    • Execution Team 2022-06-13, Execution Team 2022-06-27

    Description

      When fetching the active transaction history, we explicitly take the global lock in IS mode, but then almost immediately take further action which requires upgrading the global lock to IX mode. We want to avoid upgrading the global lock whenever possible, as it can lead to deadlock. Is it safe to take the global lock explicitly in IX mode here, or to avoid the upgrade in some other way?

      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.
          • 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

          Activity

            People

              haley.connelly@mongodb.com Haley Connelly
              dan.larkin-york@mongodb.com Dan Larkin-York
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: