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

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0.2, 4.1.3
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.0
    • Sprint:
      Repl 2018-08-27
    • Linked BF Score:
      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

          is related to

          Task - A task that needs to be done. SERVER-39610 Reformat TransactionParticipant comments and remove last references to the metrics mutex

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              matthew.russotto Matthew Russotto
              Reporter:
              matthew.russotto Matthew Russotto
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: