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

set Fetcher::_inShutdown immediately after locking in Fetcher::cancel()

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.3.11
    • Affects Version/s: 3.3.10
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 18 (08/05/16)
    • 0

      There is a race in the new initial sync code where Fetcher::cancel() can be called while we're in a previous batch's _callback() but before the next batch is scheduled. This means that Fetcher::cancel() is called when the callback handle is invalid, and thus Fetcher::_inShutdown is never set to true. The next batch is then scheduled and _inShutdown is never set to false.

            Assignee:
            judah.schvimer@mongodb.com Judah Schvimer
            Reporter:
            judah.schvimer@mongodb.com Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: