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

Improve distributed transaction commit locking behavior

    XMLWordPrintable

Details

    • Improvement
    • Status: Backlog
    • Major - P3
    • Resolution: Unresolved
    • None
    • None
    • None

    Description

      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.

      Attachments

        Issue Links

          Activity

            People

              backlog-server-execution Backlog - Storage Execution Team
              gregory.noma@mongodb.com Gregory Noma
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated: