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

Deadlock between S lock acquisition on secondary and prepare conflict

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Duplicate
    • None
    • None
    • Replication
    • ALL
    • 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

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-39096 Prepared transactions and DDL operations can deadlock on a secondary, if a reader blocks on a prepared document

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-39372 Make secondary lock acquisition for DDL operations consistent with behavior on primary

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-40705 Stepdown with prepared transaction that performed text search triggers invariant

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

          Task - A task that needs to be done. SERVER-37199 Yield locks of transactions in secondary application

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

          Task - A task that needs to be done. SERVER-38588 Hybrid index builds do not work when applied concurrently with prepared transactions on secondaries

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

          Task - A task that needs to be done. SERVER-37988 recover locks on step up at the beginning of the state transition rather than at the end

          • Minor - P4 - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-41888 Shutting down with prepared transaction can invariant during collection validation

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

          Task - A task that needs to be done. SERVER-40936 add an invariant that we do not get a prepare conflict while holding a global, database, or collection MODE_S lock

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

          Task - A task that needs to be done. SERVER-40937 remove the secondary DB lock acquisition for multikey updates

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

          Task - A task that needs to be done. SERVER-40938 Add tests that dbhash and map-reduce do not accept a read concern

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

          Activity

            People

              judah.schvimer@mongodb.com Judah Schvimer
              judah.schvimer@mongodb.com Judah Schvimer
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: