[DOCS-15832] Investigate changes in SERVER-46446: Log time spent waiting for remote operations Created: 20/Jan/23 Updated: 22/Jan/24 |
|
| Status: | Backlog |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0, 6.0.8 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | backlog, feature, query, release, server-docs-bug-bash, sharding | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 1 year, 2 weeks, 2 days ago | ||||||||
| Description |
|
Original Downstream Change Summary This change adds a new optional field, "remoteOpWaitMillis" to the profiler / slow query log lines. It tells you how much time the node spent waiting for results from other nodes. By comparing this with the total "durationMillis" you can figure out whether the merger or a shard is to blame for a slow query. This change basically expands 'remoteOpWaitMillis' to any command that contacts shards. Description of Linked Ticket This ticket is the find() counterpart of |
| Comments |
| Comment by Jeffrey Allen [ 23/Jan/23 ] |
|
Triaging to backlog. We'll move to "Ready for Work" closer to the 6.3 release. |