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

Cancelling heartbeats doesn't work after network operation scheduled

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Gone away
    • 3.0.0
    • None
    • Replication
    • None
    • Fully Compatible
    • ALL
    • v3.4, v3.2
    • Repl 2017-02-13, Repl 2017-03-06, Repl 2017-03-27
    • 0

    Description

      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.

      Attachments

        Issue Links

          is depended on by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-22523 investigate liveness timeout resetting

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-29703 Race condition when checking for callback cancellation in ReplicationCoordinator

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-21795 Do not reschedule more than one liveness timeout callback at a time

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              william.schultz@mongodb.com William Schultz (Inactive)
              scotthernandez Scott Hernandez (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: