-
Type: New Feature
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Diagnostics
-
None
-
Query
-
(copied to CRM)
If a db.eval parent op is constantly generating new child ops, the parent op is unlikely to be visible with currentOp. The currentOp implementation should show an op's parent's num so a user can kill the parent.
Alternatively currentOp could show the full op info for parent ops.
- is related to
-
SERVER-1928 evald fails in small oplog test
- Closed
- related to
-
SERVER-387 currentOp() and killOp() don't work right with db.eval()
- Closed