[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: |
|
||||||||||||
| 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 ] |
|
|
| Comment by Alon Horev [ 15/May/14 ] |
|
If I understand |
| Comment by Eliot Horowitz (Inactive) [ 15/May/14 ] |
|
Full fix is in |