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

Avoid taking any lock manager locks in the killCursors code path

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Querying
    • Query Execution
    • 0

      In the killCursors code path we acquire a collection lock via AutoStatsTracker which could cause a deadlock (e.g., when there is a parallel DDL task queueing up on taking a Global X lock). Ideally, we'd want to re-design the killCursors code path to avoid any lock manager locks. Once it is done, the test from SERVER-35567 can be re-enabled (note that the test will require some modifications to avoid getting stuck in the killSessions state, see comments to SERVER-35567 for details).

            backlog-query-execution [DO NOT USE] Backlog - Query Execution
            anton.korshunov@mongodb.com Anton Korshunov
            0 Vote for this issue
            7 Start watching this issue