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

kill_cursors_in_transaction.js should check for pending drop using $currentOp

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.0.0-rc2, 4.1.1
    • Affects Version/s: 4.0.0-rc1
    • Component/s: Replication
    • Labels:
      None
    • Fully Compatible
    • ALL
    • v4.0
    • Repl 2018-06-04, Repl 2018-06-18
    • 15

      kill_cursors_in_transaction.js currently checks that a drop has a pending X database lock by running a find with maxTimeMS and checking that it times out. This can hang if the find is profiled, since profiling will wait for an IX database lock and does not respect maxTimeMS. Instead, we should check that the drop has a pending X database lock using a $currentOp aggregation, which does not take locks.

            Assignee:
            tess.avitabile@mongodb.com Tess Avitabile (Inactive)
            Reporter:
            tess.avitabile@mongodb.com Tess Avitabile (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: