[SERVER-59714] Include number of calls to mongot in slow query log Created: 01/Sep/21 Updated: 29/Oct/23 Resolved: 12/Oct/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.2.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Oren Ovadia | Assignee: | Ted Tuckman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | QO 2021-10-18 |
| Participants: |
| Description |
|
Slow query log for $search queries and getMores includes this section today:
I suggest we include the number of getMores calls to mongot performed. For long running queries with a blocking stage such as $group and $sort, this will be very useful for debugging purposes. This will be incredibly important if we ever pushdown $limit to mongot, and when mongot will be returning variable batch sizes.
|
| Comments |
| Comment by Oren Ovadia [ 13/Oct/21 ] |
|
Thanks Ted! |
| Comment by Githook User [ 12/Oct/21 ] |
|
Author: {'name': 'Ted Tuckman', 'email': 'ted.tuckman@mongodb.com', 'username': 'TedTuckman'}Message: |
| Comment by Githook User [ 12/Oct/21 ] |
|
Author: {'name': 'Ted Tuckman', 'email': 'ted.tuckman@mongodb.com', 'username': 'TedTuckman'}Message: |