-
Type: Bug
-
Resolution: Done
-
Priority: 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(
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.
- related to
-
SERVER-7059 renamedatabase blocks
- Closed