[SERVER-27212] Allow configuration for "query not recording (too large)" Created: 29/Nov/16 Updated: 06/Dec/22 Resolved: 09/Dec/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics, Logging |
| Affects Version/s: | 3.2.11 |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Brad Vogel | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Query
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Following issue https://jira.mongodb.org/browse/SERVER-5605, we're seeing "query not recording (too large)" when running db.currentOp() to try to track down our slow db queries. It's frustrating not to be able to find the exact query. We're heavy users of Mongo aggregations - some not really even that long in my opinion - but we're finding that all are "too large" to be recorded. Can a setting be added to override the size that Mongo considers "too large"? We'd use this to make sure most of our queries are recorded using `db.currentOp()` and the slow query log - to help us track down potential issues. |
| Comments |
| Comment by Brad Vogel [ 09/Dec/16 ] |
|
Thanks! |
| Comment by James Wahlin [ 09/Dec/16 ] |
|
brad@mixmax.com - I am going to close this ticket given 50kB of query content should in most cases be sufficient to track down the origin. As mentioned, this change is available starting in MongoDB 3.4. If this solution is not sufficient for your use case please feel free to reopen and provide details. Best, |
| Comment by James Wahlin [ 09/Dec/16 ] |
|
While not configurable, work was done under
This change is available in MongoDB 3.4 |