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

Fix race in CompatibleFirstStress lock manager test

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Trivial - P5
    • Resolution: Fixed
    • 3.7.1
    • 3.4.11, 3.6.2, 3.7.1
    • Storage
    • None
    • Fully Compatible
    • v3.6, v3.4
    • Storage 2017-12-18
    • 0

    Description

      A call to lockComplete with timeout 0 may return LOCK_WAITING even though another thread already was notified. So the invariant that lockComplete must succeed if another thread is holding a MODE_S lock is invalid.

       

      Attachments

        Activity

          People

            geert.bosch@mongodb.com Geert Bosch
            geert.bosch@mongodb.com Geert Bosch
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: