Possible deadlock when returning connection to connection pool

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Networking & Observability
    • ALL
    • Egress gRPC 2025-02-14, N&O 2025-03-17, N&O 2025-03-31, N&O 2025-04-14, N&O 2025-04-28
    • 200
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      In the custom deleter for connection pool ConnectionHandles, we acquire a mutex here, and then call updateState. updateState then schedules a task on an executor, which will acquire that same mutex. Due to SERVER-93029, we may run that task inline, but we are already holding the lock, and so there may be a deadlock.

            Assignee:
            Erin McNulty
            Reporter:
            Erin McNulty
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: