Reset stopTimestamp in DataReplicator when initial sync apply phase tries to fetch a remote document

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 3.4.0-rc2
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2016-10-31
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When the oplog applier fetches a document from our sync source, we must get the latest optime from the sync source, and set that as our stopTimestamp. That way we will not finish initial sync until our data is all from a consistent point.

              Assignee:
              Judah Schvimer
              Reporter:
              Judah Schvimer
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: