[SERVER-14990] Do not omit the information about the batch if its too big Created: 21/Aug/14  Updated: 25/Jun/15  Resolved: 18/Feb/15

Status: Closed
Project: Core Server
Component/s: Logging, Querying
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Alexander Komyagin Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: polish
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-16324 Command execution log line displays "... Closed
Related
is related to SERVER-6218 Profile documents should include part... Closed
Operating System: ALL
Participants:

 Description   

This is an example of line that we log for small (2 docs) batch inserts:

2014-08-21T12:26:32.909-0400 [conn4] command test.$cmd command: insert { insert: "test", documents: 2, ordered: true } keyUpdates:0 numYields:0 locks(micros) w:292 reslen:40 285ms

This is when the batch is big (10000 inserts):

2014-08-21T12:29:39.264-0400 [conn5] command test.$cmd command: insert { $msg: "query not recording (too large)" } keyUpdates:0 numYields:0 locks(micros) w:345 reslen:40 128ms

It's easy to see that the latter line is practically useless for diagnostic purposes as it has no information about the batch itself at all.



 Comments   
Comment by J Rassi [ 18/Feb/15 ]

Confirmed as dup of SERVER-16324.

Comment by Matt Kangas [ 27/Sep/14 ]

I believe this is closely related to SERVER-6218, possibly the same root cause.

Generated at Thu Feb 08 03:36:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.