[SERVER-57406] add queryHash and planCacheKey to mongod slow query logs for update and delete requests Created: 03/Jun/21 Updated: 17/Nov/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Mickey Winters | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | query-offsite | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Query Execution
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Right now the queryHash is passed around in the current operations debug context and there is only room for one queryHash and planCacheKey, but with multiple batched updates/deletes each item in the batch could have a different query shape and a different queryHash as a consequence. We need to decide if we are going to log a list of the query hashes or just the hash of the first item. |
| Comments |
| Comment by Mickey Winters [ 07/Nov/23 ] |
|
charlie.swanson@mongodb.com do you think https://jira.mongodb.org/browse/SERVER-57404 is also related and has there been any updates on that decision |