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

Deadlock between shutdown and stepdown

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.4.5, 3.5.6
    • Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2017-05-08
    • 0

    Description

      Stepdown calls ReplicationCoordinatorExternalStateImpl::startProducerIfStopped, which takes _threadMutex while holding the global exclusive lock. Shutdown calls ReplicationCoordinatorExternalStateImpl::shutdown which takes _threadMutex and then does a database read by calling _storageInterface->getAppliedThrough.

      We should probably be doing the database reads/writes in ReplicationCoordinatorExternalStateImpl::shutdown after releasing _threadMutex.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-33186 Primary node may deadlock during shutdown

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-7200 use oplog as op buffer on secondaries

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

          Activity

            People

              benety.goh@mongodb.com Benety Goh
              spencer@mongodb.com Spencer Brody (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: