[SERVER-71062] Hedged async RPC runner should use dynamic backoff instead of delay Created: 03/Nov/22 Updated: 29/Oct/23 Resolved: 08/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | George Wangensteen | Assignee: | George Wangensteen |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Service Arch 2022-11-14 |
| Participants: |
| Description |
|
The hedged async RPC runner (async_rpc::sendHedgedCommand) is mistakenly using a fixed delay between retry attempts instead of a dynamic one - it only calls getNextRetryDelay once and uses that value for each retry, instead of calculating a new value between each retry attempt. We should fix this and add a test for it. |
| Comments |
| Comment by Githook User [ 08/Nov/22 ] |
|
Author: {'name': 'George Wangensteen', 'email': 'george.wangensteen@mongodb.com', 'username': 'gewa24'}Message: |