Improve distributed transaction commit locking behavior

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • Fully Compatible
    • CAR Team 2023-12-25
    • 3
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      In a distributed transaction, when the coordinator writes its commit decision, it takes global/db/collection locks to do so while the participant is also still holding the global lock. This can cause issues when combined with operations that take strong global locks, as seen in SERVER-65821. We should investigate ways to improve this behavior so that we can remove the workaround added in that ticket. One potential idea is to consolidate the participant and coordinator on the coordinating shard, so that they can make progress with a single set of resources.

            Assignee:
            Josef Ahmad
            Reporter:
            Gregory Noma
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: