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

Deadlock on restarting the node with a prepared transaction acquiring the global lock

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major - P3
    • Resolution: Unresolved
    • None
    • None
    • None
    • None
    • Replication
    • ALL
    • 6

    Description

      Acquiring the global lock in the initAndListen function while initialization mongod after starting up replication is dangerous as we might reconstruct a prepared transaction which acquire the global lock and keep it, which will cause a deadlock.

       

       

      You can repro it by adding a sleep before this line and run jstests/replsets/ddl_op_behind_transaction_fails_in_shutdown.js

      Attachments

        Issue Links

          is caused by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-56644 local.system.resharding.slimOplogForGraphLookup isn't created when replica set has already been initiated

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

          Task - A task that needs to be done. SERVER-67605 Make retryable_findAndModify_commit_and_abort_prepared_txns_after_failover_and_restart.js not test restart with a 1-node shard

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

          Activity

            People

              backlog-server-repl Backlog - Replication Team
              m.maher@mongodb.com Moustafa Maher
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated: