[SERVER-57404] add queryHash to mongos slow query logs for batched 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 |
|
fixing this for non batched updates and deletes is going to be fixed by https://jira.mongodb.org/browse/SERVER-57405 part of the problem why that ticket didn't also fix batched update and deletes is because right now the queryHash is passed around in the current operations debug context and there is only room for one queryHash, 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. |