[SERVER-72670] Change hedgingMetrics.numTotalHedgedOperations increment to reflect definition in documentation Created: 10/Jan/23 Updated: 29/Oct/23 Resolved: 07/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Alex Li | Assignee: | Alex Li |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Service Arch
|
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Service Arch 2023-01-23, Service Arch 2023-02-06, Service Arch 2023-02-20 |
| Participants: |
| Description |
|
Currently, both async_rpc and NetworkInterfaceTL increment hedging metrics in a similar way. One of the metrics, numTotalHedgedOperations, is currently incremented once for each additional RPC sent for each hedged operation. The documentation describes numTotalHedgedOperations as "the number of all operations for which the mongos instance hedged the read operation." Fix the mismatch. |
| Comments |
| Comment by Githook User [ 06/Feb/23 ] |
|
Author: {'name': 'Alex Li', 'email': 'alex.li@mongodb.com', 'username': 'lia394126'}Message: |