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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.4.0-rc3
    • Fix Version/s: 3.4.2, 3.5.1
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v3.4
    • Sprint:
      Repl 2016-11-21
    • Linked BF Score:
      0

      Description

      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.

        Attachments

          Issue Links

          is depended on by

          Task - A task that needs to be done. SERVER-27098 review and fix log levels in DataReplicator

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-27052 Add asynchronous operation support to DataReplicator

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

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: