Handle out-of-order killOperations command

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Networking & Observability
    • Service Arch 2023-05-01, N&O Prioritized List
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Unassigned
              Reporter:
              Benjamin Caimano (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: