-
Type: Bug
-
Resolution: Done
-
Priority: Minor - P4
-
Affects Version/s: None
-
Component/s: JavaScript
-
None
currentOp() doesn't indicate an eval is in progress.
killOp() won't kill it either.
- depends on
-
SERVER-1610 curop seg fault
- Closed
-
SERVER-1816 killop not robust
- Closed
-
SERVER-1840 in v8, can't do a $where with a function() inside of db.eval
- Closed
-
SERVER-1841 in spidermonkey js impl, killop can be caught as a js exception
- Closed
-
SERVER-1844 killop does not work for nested ops
- Closed
-
SERVER-1900 v8 Issue 708
- Closed
-
SERVER-2076 killall may fail in v8
- Closed
-
SERVER-2225 when multiple map reduce jobs are running and one is holding the js mutex indefinitely, it is not obvious which is hogging the js mutex
- Closed
- is related to
-
SERVER-1931 curop should show op num of parent ops
- Closed