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

Running shouldStopIteration inline in AsyncTryUntilWithDelay can create deadlock

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Gone away
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Service Arch
    • ALL
    • 4

    Description

      It's possible for the following to happen:

      1. Service acquires mutex mx and invokes some cleanup work.
      2. As part of cleanup, call setError on owned promises.
      3. AsyncTryUntilWithDelay::runImpl reaches the end of an iteration and invokes shouldStopIteration inline, but shouldStopIteration also acquires mx.
      4. We get a deadlock because the service is unable to finish the cleanup work while holding the mutex, but AsyncTryUntilWithDelay is stuck waiting on the mutex.

      Attachments

        Activity

          People

            backlog-server-servicearch Backlog - Service Architecture
            jason.chan@mongodb.com Jason Chan
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: