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

Deadlock involving commands acquiring global X lock and prepared transactions waiting for write concern

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Operating System:
      ALL
    • Backport Requested:
      v4.2
    • Sprint:
      Repl 2019-10-21, Repl 2019-11-04
    • Linked BF Score:
      16

      Description

      DropDatabase or any commands that acquire the global lock in X mode can be blocked by prepared transactions. The enqueued global X lock can block oplog queries which need the global IS lock. If these oplog queries and the data replication are needed by the prepared transaction's write concern, then the prepare transaction cannot make progress. Thus a deadlock occurs.

      In reality, the coordinator may time out and decide to abort the transaction, but this could be an issue for testing.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                16 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: