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

renameCollection op is blocking, and killOp does not kill

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.0.4
    • Component/s: Concurrency, Performance, Stability, Tools
    • Environment:
      1) SMP Thu Mar 22 08:00:08 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
      2) A 5 node replica set environment.
      3) 99% idle IO stat
      4) 70GB collection


    • Linux

      During the execution of:
      > db.runCommand(

      { renameCollection: "mydb.oldname", to: "mydb.newname" }

      What happened:
      Suddenly all the operations started to stack up. Collection in question was over 70GB.

      What was expected:
      It was expected that the operation would yield. Or at the very least such behavior should be documented...

      Related:
      db.killOp() - did NOT kill the operation
      db.currentOP() - reported the OP as killed (killed:true), yet all the other ops never got executed. Additionally all the new ops continued to fill up the queue.

            Assignee:
            schwerin@mongodb.com Andy Schwerin
            Reporter:
            rl RL
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: