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

Reverse order of TransactionParticipant (Session in 4.0) and Client locks

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.0.2, 4.1.3
    • Replication
    • None
    • Fully Compatible
    • ALL
    • v4.0
    • Repl 2018-08-27
    • 46

    Description

      The Client lock is a spin lock which should be acquired last and held for as short a duration as practical. We should therefore acquire it after acquiring the TransactionParticipant mutex when changing the locker on the OperationContext.

      Attachments

        Issue Links

          Activity

            People

              matthew.russotto@mongodb.com Matthew Russotto
              matthew.russotto@mongodb.com Matthew Russotto
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: