Currently, the code for doing batch write-command inserts does all the inserts under one CurOp and only profiles that one operation. It's not currently possible to interrupt the batch in the middle of inserts, and thus $maxTimeMS doesn't work either.
Also, by profiling the one CurOp explicitly, this means the batch insert will get profiled twice and might register two profile documents (once in WriteBatchExecutor::execInserts()and once as part of assembleResponse()).
- is depended on by
-
SERVER-12926 Insert write commands on documents >=512 bytes not logged with partial doc display
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- related to
-
-
- Closed
-