[SERVER-74466] Attach OperationKey in async_rpc for non hedged requests Created: 28/Feb/23 Updated: 29/Oct/23 Resolved: 01/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Amirsaman Memaripour | Assignee: | Alex Li |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Service Arch
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | 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, Service Arch 2023-06-12 | ||||||||
| Participants: | |||||||||
| Description |
|
This is a split from Notes from the original ticket:
Update: For non hedged operations, async_rpc only deals with request and response, and does nothing to progress the operation past this layer. This means async_rpc would not need to do any extra work to deal with cancellation for non hedged operations. The new intention with the ticket is to still append an OperationKey to all operations and test the functionality in the async_rpc layer. Then, test that the OperationKey can be passed into the NetworkInterfaceTL layer. NetworkInterfaceTL already has cancellation and killOperation functionality, and the async_rpc layer has cancellation and killOperation functionality for hedged operations. End to end testing is not possible because there are no operations that currently use async_rpc, so we only test that the OperationKey can be accepted and propagated into each of the 2 layers. |
| Comments |
| Comment by Githook User [ 01/Jun/23 ] |
|
Author: {'name': 'Alex Li', 'email': 'alex.li@mongodb.com', 'username': 'lia394126'}Message: |