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

Disable problematic timeseries concurrency test until deadlock is fixed

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.9.0
    • None
    • None
    • None
    • Fully Compatible
    • ALL
    • Execution Team 2021-03-22
    • 146

    Description

      Currently there is one place where there is a lock order inversion in the BucketCatalog, where a caller tries to take a lock on the stats mutex while holding a lock on a bucket mutex. This leads to deadlock (and subsequently test timeouts) in jstests/concurrency/fsm_workloads/create_timeseries_collection.js. The underlying behavior should be fixed by SERVER-54985 which is currently under review. Until it is merged, we can simply disable the test and later re-enable it.

      Attachments

        Activity

          People

            dan.larkin-york@mongodb.com Dan Larkin-York
            dan.larkin-york@mongodb.com Dan Larkin-York
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: