VoteRequestor and FreshnessChecker need safe destruction

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.5.13
    • Affects Version/s: None
    • Component/s: Replication
    • Fully Compatible
    • ALL
    • Repl 2017-07-31, Repl 2017-08-21, Repl 2017-09-11
    • 15
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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

              Assignee:
              Siyuan Zhou
              Reporter:
              Matthew Russotto
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: