If I create an index, the operation statistics reported do not include the statistics from the IndexBuildsCoordinator thread that built the index.
e.g:
command test.Collection0 command: createIndexes { createIndexes: "Collection0", ... numYields:0 reslen:257 locks:{ ParallelBatchWriterMode: { acquireCount: { r: 3 } }, ReplicationStateTransition: { acquireCount: { w: 4 } }, Global: { acquireCount: { r: 1, w: 3 } }, Database: { acquireCount: { r: 1, w: 3 } }, Collection: { acquireCount: { w: 1, W: 2 } }, Mutex: { acquireCount: { r: 4 } } } flowControl:{ acquireCount: 2 } storage:{} protocol:op_msg 36458ms
This would have previously reported the following:
- numYields > 0 due to yielding
- high lock acquisitions due to yielding
- storage statistics for the number of bytes read and written
- is related to
-
SERVER-39218 Simultaneous index builds improvements to currentOp output for createIndexes
-
- Closed
-