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

Deadlock between S lock acquisition on secondary and prepare conflict

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Replication
    • Labels:
    • Operating System:
      ALL
    • Sprint:
      Repl 2019-05-06

      Description

      The following deadlock can occur:
      1) A transaction goes in prepare in oplog application
      2) A user operation acquires a lock in mode S and then blocks on a prepare conflict with the prepared transaction.
      3) The commit of the prepared transaction attempts to reacquire (since the lock was yielded) an IX lock that conflicts with the mode S lock and blocks.

      Possible solutions:
      1) Do not yield locks for prepared transactions on secondaries.
      2) Say such a user operation is illegal. We do not think they can occur today.
      3) Yield locks in prepare conflicts

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              judah.schvimer Judah Schvimer
              Reporter:
              judah.schvimer Judah Schvimer
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: