[SERVER-2207] mongod outputs large queries in full Created: 10/Dec/10  Updated: 12/Jul/16  Resolved: 06/Jul/12

Status: Closed
Project: Core Server
Component/s: Performance
Affects Version/s: 1.6.4
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Andreas Svensson Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-1591 don't use a StringBuilder in OpDebug Closed
Operating System: ALL
Participants:

 Description   

mongod outputs all (slow?) queries, in full, to the console (even with profiling disabled). This is an issue when using $in with a very large set of values/ids. As detailed in the post below, specifying some 130 000 ids for retrieval causes the ENTIRE QUERY to be output to the console, meaning some 50 000 lines which takes considerable time.

http://groups.google.com/group/mongodb-user/msg/4045e74f8756b4ef



 Comments   
Comment by Eliot Horowitz (Inactive) [ 06/Jul/12 ]

This was done a while back

Comment by Andreas Svensson [ 14/Dec/10 ]

The most flexible solution could perhaps be to just have it user-defined as well, like the "slowms". And if it's longer than that, then perhaps cut off the end like "abcdefgh... (2123 chars)", or perhaps better cut it in the middle "abcd... (2123 chars) ...efgh", cutting the middle could be useful as there might be "sensible" queries before or after "something very long".

Comment by Eliot Horowitz (Inactive) [ 14/Dec/10 ]

We need to be careful with how we make this change as often those kinds of queries are the slow ones, so losing debugging information is bad.

Comment by Antoine Girbal [ 13/Dec/10 ]

we will add a limit of size for the output.
As a workaround, you can set slowms to a value much larger than 100ms.

Generated at Thu Feb 08 02:59:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.