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

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Execution Team 2022-06-13, Execution Team 2022-06-27
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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?

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

              Created:
              Updated:
              Resolved: