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

DataReplicator should wait for last oplog fetcher to finish before starting next initial sync attempt

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.4.2, 3.5.1
    • Affects Version/s: 3.4.0-rc3
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • v3.4
    • Repl 2016-11-21
    • 0

      DataReplicator::_anyActiveHandles_inlock() and DataReplicator::_waitOnAndResetAll_inlock() are not checking _lastOplogFetcher. This may cause delayed _lastOplogFetcher callbacks to run during the next initial sync attempt.

            Assignee:
            benety.goh@mongodb.com Benety Goh
            Reporter:
            benety.goh@mongodb.com Benety Goh
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: