[SERVER-48174] Add log component and LOGV2 messages in server to measure latency of migration protocol stages Created: 12/May/20 Updated: 29/Oct/23 Resolved: 25/Jun/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Alexander Taskov (Inactive) | 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 2020-06-01, Sharding 2020-06-15, Sharding 2020-06-29 | ||||||||
| Participants: | |||||||||
| Description |
|
Instrument the C++ code to measure: total latency = majority commit wait on recipient (1) |
| Comments |
| Comment by Githook User [ 25/Jun/20 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com'}Message: |