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

clear oplog before starting initial sync

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 2.8.0-rc1
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • ALL

      If an initial sync encounters a problem any time after the first oplog sync phase, it can leave data behind in the oplog. When the node is restarted, another initial sync begins automatically, but the code isn't set up to work properly in the presence of data preexisting in the oplog. We need to clear out the old data before beginning a new initial sync.

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

              Created:
              Updated:
              Resolved: