[SERVER-13935] Allow specifying profile entry and currentOp max query size Created: 14/May/14  Updated: 10/Dec/14  Resolved: 15/May/14

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

Type: New Feature Priority: Major - P3
Reporter: Alon Horev Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-1794 make CurOp query's lifespan same as t... Closed
is related to SERVER-13952 Cache partial BSONObj if possible (in... Closed
Participants:

 Description   

When debugging long running queries, they're often too big and don't appear in db.currentOp():

"query" :

{ "$msg" : "query not recording (too large)" }

,

Additionally, they don't appear in system.profile:

"err" : "profile line too large (max is 100KB)",

This makes it impossible for us to understand what's hammering the database.

It would be nice to have a parameter similar to profiling level. something like profile size.

I don't mind adding it myself (including tests) but my last pull request was practically ignored.



 Comments   
Comment by Eliot Horowitz (Inactive) [ 15/May/14 ]

SERVER-1794 will allow us to show an entire query.

Comment by Alon Horev [ 15/May/14 ]

If I understand SERVER-1794 correctly it should show a partial query. What do you think about configuring the maximum size of an object to be profiled? (it sounds like 'extract a variable to be a parameter' so it also sounds easy to solve)

Comment by Eliot Horowitz (Inactive) [ 15/May/14 ]

Full fix is in SERVER-1794

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