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

Oplog application during initial sync should be exclusive of the start/minValid oplog entry

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Minor - P4 Minor - P4
    • None
    • None
    • Replication
    • None
    • ALL

    Description

      At the beginning of initial sync, we take note of the current most recent document in the primary's oplog. After cloning the data, we apply the oplog for all entries newer than and including the entry that was noted to start with. We should only apply entries newer than the initial one. This can cause problems when users do complex backup/restore procedures where the document referred to by the most recent oplog entry ceased to exist because of modifications to the file system outside of MongoDB.

      Attachments

        Activity

          People

            Unassigned Unassigned
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: