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

resync command should clear lastOpTimeWritten in oplog.cpp

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 2.6.0-rc0
    • Affects Version/s: 2.5.5
    • Component/s: Replication
    • None
    • ALL
    • Hide

      Run the resync command and during initial sync you will see the "replication oplog stream went back in time." message in the server log, and it will redirect syncing back to the primary.

      Show
      Run the resync command and during initial sync you will see the "replication oplog stream went back in time." message in the server log, and it will redirect syncing back to the primary.

      Otherwise, logOp gets annoyed because it thinks we are logging the same op as last time, even though we have cleared out the oplog so it's a non-issue.

            Assignee:
            milkie@mongodb.com Eric Milkie
            Reporter:
            milkie@mongodb.com Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: