[SERVER-73779] Add maxTimeMSOpOnly to network message if it is a hedge sent through async_rpc API Created: 08/Feb/23 Updated: 29/Oct/23 Resolved: 16/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | George Wangensteen | 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 |
| Sprint: | Service Arch 2023-02-20, Service Arch 2023-03-06, Service Arch 2023-03-20, Service Arch 2023-04-03, Service Arch 2023-04-17, Service Arch 2023-05-01, Service Arch 2023-05-15, Service Arch 2023-05-29 |
| Participants: |
| Description |
|
The 'hedges' of an operation should have a maxTimeMSOpOnly expiration attached to them to prevent overload by executing a resource intensive/long running operation on multiple machines. See https://jira.mongodb.org/browse/SERVER-46472 for the original motivation, and https://jira.mongodb.org/browse/SERVER-47117 for why it needs to be maxTimeMSOpOnly instead of the ordinary maxTimeMS. We need to ensure the async API adds this to it's own hedges. |
| Comments |
| Comment by Githook User [ 16/May/23 ] |
|
Author: {'name': 'Alex Li', 'email': 'alex.li@mongodb.com', 'username': 'lia394126'}Message: |