[SERVER-67253] Track time spent waiting for refresh on the router Created: 14/Jun/22 Updated: 29/Oct/23 Resolved: 26/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | Allison Easton |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Sharding EMEA 2022-06-27, Sharding EMEA 2022-07-11, Sharding EMEA 2022-07-25, Sharding EMEA 2022-08-08 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
As a second part of tracking the time CRUD operations spend waiting for metadata refresh, we should add to the slow query log the time taken waiting for routing information. This could potentially reuse the timing in totalRefreshWaitTimeMicros. |
| Comments |
| Comment by Githook User [ 26/Jul/22 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |