[SERVER-54571] queryHash and planCacheKey Fields Absent in getMore Requests Created: 15/Feb/21 Updated: 29/Oct/23 Resolved: 19/Aug/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework, Diagnostics, Logging, Querying |
| Affects Version/s: | 4.2.12, 4.4.4 |
| Fix Version/s: | 5.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Diego Rodriguez (Inactive) | Assignee: | Mickey Winters |
| Resolution: | Fixed | Votes: | 3 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v5.0, v4.4, v4.2
|
||||||||||||
| Sprint: | Query Execution 2021-05-31, Query Execution 2021-06-14, Query Execution 2021-06-28, Query Execution 2021-07-12, Query Execution 2021-07-26, QE 2021-08-09, QE 2021-08-23 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Hi Team, Starting in v4.2, MongoDB introduced the queryHash and planCacheKey that respectively help identify slow queries with the same query shape and the plan cache entry associated with the query. Said fields are present in the log from the initial batch for a "slow" query:
But are absent from any subsequent getMore requests:
This happens for both find and aggregate operations in both v4.2.12 and v4.4.4. It would be nice to have these fields present in the getMore requests as not having them makes troubleshooting more difficult and/or inaccurate when using those fields as an analysis criteria, for example:
Regards |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 19/Aug/21 ] |
|
Author: {'name': 'Mickey. J Winters', 'email': 'mickey.winters@mongodb.com', 'username': 'mjrb'}Message: |