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

VoteRequestor and FreshnessChecker need safe destruction

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.5.13
    • Component/s: Replication
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Repl 2017-07-31, Repl 2017-08-21, Repl 2017-09-11

      Description

      The VoteRequester and FreshnessChecker can be destroyed with callbacks still pending on their ScatterGatherRunner. Since the callbacks access the ScatterGatherRunner::Algorithm owned by the VoteRequestor/FreshnesssChecker, this can result in various bad behavior (crashes or memory corruption leading to just about anything). The ScatterGatherRunner::Algorithm needs to live until all callbacks are complete.

      This would probably make sense to combine with SERVER-28389

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: