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

Avoid taking any lock manager locks in the killCursors code path

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Backlog
    • Major - P3
    • Resolution: Unresolved
    • None
    • None
    • Querying
    • Query Execution
    • 0

    Description

      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).

      Attachments

        Issue Links

          is related to

          Task - A task that needs to be done. SERVER-35567 Concurrency simultaneous replication tests - unblacklist snapshot_read_kill_operations.js and remove snapshot_read_kill_op_only.js

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-40058 AutoStatsTracker's lock acquisition to read the profiling level should not conflict with secondary batch application

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              backlog-query-execution Backlog - Query Execution
              anton.korshunov@mongodb.com Anton Korshunov
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated: