-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Critical - P2
-
None
-
Affects Version/s: 2.6.0-rc0
-
Component/s: Logging
-
Labels:None
-
ALL
With the new write commands API, logged operations do not carry a lot of useful statistics at all:
2014-02-26T17:42:02.664-0500 [conn1] command test.$cmd command: { insert: "foo", documents: [ { _id: ObjectId('530e6dbaed9a16e31683ccce'), foo: "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa..." } ], ordered: true } keyUpdates:0 numYields:0 reslen:40 0ms
In order for these log messages to be useful (comparable to 2.4), we need to consider adding at least the following:
- time under write lock
- number of operations in the batch
- number of inserted/updated/removed docs
- duplicates
-
SERVER-12762 Batch inserts should be counted and profiled individually
-
- Closed
-
- is related to
-
-
- Closed
-
- related to
-
-
- Backlog
-