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

kill_cursors_in_transaction.js should check for pending drop using $currentOp

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 4.0.0-rc1
    • Fix Version/s: 4.0.0-rc2, 4.1.1
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.0
    • Sprint:
      Repl 2018-06-04, Repl 2018-06-18
    • Linked BF Score:
      15

      Description

      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.

        Attachments

          Activity

            People

            Assignee:
            tess.avitabile Tess Avitabile
            Reporter:
            tess.avitabile Tess Avitabile
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: