[SERVER-51709] Handle out-of-order killOperations command Created: 16/Oct/20 Updated: 18/Jul/23 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Benjamin Caimano (Inactive) | Assignee: | Backlog - Service Architecture |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | ben-sa-triage, techdebt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Service Arch
|
| Sprint: | Service Arch Prioritized List, Service Arch 2023-05-01 |
| Participants: |
| Description |
|
Since the killOperations command can race over the network, I think a more complete solution is needed. My proposal is a background service that tracks OperationKey values by HostAndPort. Consumer would add an OperationKey with a HostAndPort and an optional deadline. Then the service will include it in a regularly scheduled killOperations after that deadline that it sends to that HostAndPort. Consumers would have to explicitly remove that OperationKey once their operation resolves either naturally or from cancelation. |
| Comments |
| Comment by Blake Oler [ 26/Jan/23 ] |
|
TODO: Repurpose this ticket into generically asking for a solution to the killOp command racing over the network. |
| Comment by Lauren Lewis (Inactive) [ 18/Mar/22 ] |
|
We haven’t heard back from you for some time, so we're going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket. |