Release lock before destroying DBClientBases

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.3.3
    • Affects Version/s: None
    • Component/s: Networking, Sharding
    • None
    • Fully Compatible
    • ALL
    • 21
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Benjamin Caimano (Inactive)
            Reporter:
            Matthew Saltz (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: