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

Release lock before destroying DBClientBases

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.3.3
    • None
    • Networking, Sharding
    • None
    • Fully Compatible
    • ALL
    • 21

    Description

      An error occurs in testing because DBConnectionPool acquires its mutex (declared here at acquisition level 0) in this function which eventually tries to acquire this latch which was declared here at lock level 0, causing an InvalidWasPresent error. We should reconsider the lock level in DBConnectionPool maybe, or reconsider whether it is necessary to have a mutex in ConnectionShardStatus.

      Attachments

        Activity

          People

            ben.caimano@mongodb.com Benjamin Caimano (Inactive)
            matthew.saltz@mongodb.com Matthew Saltz (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: