Cancelling heartbeats doesn't work after network operation scheduled

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: 3.0.0
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • v3.4, v3.2
    • Repl 2017-02-13, Repl 2017-03-06, Repl 2017-03-27
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      When cancelling a heartbeat after it has scheduled the network operation, cancel doesn't work correctly from the client perspective because the handle that is cancelled is not the network operation. This is due to how we schedule work which then schedules the network operation, which does the callback (and reschedules more the next heartbeat).

      One idea to fix this would be to keep a CancellableHandle which gets replaced with the newly scheduled network event so that a client can cancel the logical operation at any time.

            Assignee:
            Will Schultz
            Reporter:
            Scott Hernandez (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: