-
Type: New Feature
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.4.10
-
Component/s: Querying
-
None
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.
- is related to
-
SERVER-13952 Cache partial BSONObj if possible (instead of {$msg: "query not recording (too large)"})
- Closed
- related to
-
SERVER-1794 make CurOp query's lifespan same as the op - so we can just keep a pointer
- Closed