Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-51709

Handle out-of-order killOperations command

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Service Arch
    • Service Arch 2023-05-01, N&O Prioritized List

      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:
            backlog-server-servicearch [DO NOT USE] Backlog - Service Architecture
            Reporter:
            ben.caimano@mongodb.com Benjamin Caimano (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: