I had an ugly script that was launching several MapReduce tasks consequently and handled the execution progress in each of them to show nice messages like "done: 75%" and ensure that no MapReduce task will be executed concurrently with another reducing performance of both.

It relied heavily on the output of currentOp(or, to be precise, on the contents on $cmd.sys.inprog collection), using "query" parameter to find command in the list of currently executing commands. However, when I updated to 2.4.0, db.currentOp shows

"query" :

{ "$msg" : "query not recording (too large)" }

,
for all my MapReduce tasks, thus breaking my observer script and laying raid to my cattle. Has there been any logic behind hiding query information in currentOp?