[SERVER-387] currentOp() and killOp() don't work right with db.eval() - MongoDB

XML

Word

Printable

currentOp() doesn't indicate an eval is in progress.

killOp() won't kill it either.

depends on

SERVER-1610 curop seg fault

SERVER-1816 killop not robust

SERVER-1840 in v8, can't do a $where with a function() inside of db.eval

SERVER-1841 in spidermonkey js impl, killop can be caught as a js exception

SERVER-1844 killop does not work for nested ops

SERVER-1900 v8 Issue 708

SERVER-2076 killall may fail in v8

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

is related to

SERVER-1931 curop should show op num of parent ops

(3 depends on, 1 is related to)