[SERVER-18173] Being able to control the length of 'query not recording (too large)' message Created: 22/Apr/15 Updated: 22/Apr/15 Resolved: 22/Apr/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Alex Lerner | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Is it possible to have a config setting that controls the length of "too long to display" messages in the log file? This is particularly useful when trying to debug queries that are too long for display and which show up as part of findAndModify() entries. |
| Comments |
| Comment by J Rassi [ 22/Apr/15 ] |
|
The diagnostic log should no longer contain such "too long to display" messages. As of 2.6.6, the "slow query" log messages for commmands include the full query object ( As of 3.0.0, the restriction that findAndModify operations with a sort are not allowed to yield has been lifted ( As such, I am closing this ticket as a duplicate of |