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

Do not reset numGetMoreOplogEntries in GetInitialSyncProgress test in DataReplicatorTest

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Repl 2016-12-12
    • 0

      There's no reason to reset numGetMoreOplogEntries here, and it can lead to OplogOutOfOrder errors.

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

              Created:
              Updated:
              Resolved: