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

Add Replica Set Restore Mode (for point-in-time)

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Investigating
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Admin, Replication
    • Labels:
      None
    • Operating System:
      ALL
    • Linked BF Score:
      0

      Description

      This mode/command will need to support situations where unique indexes restraints must be loosened like during initial-sync/recovery mode.

      Depending on the state of the data, and the contents of the oplog, in a backup taken with "mongodump --oplog", attempting to restore the data may cause temporary unique-index violations. The violations will be resolved by the time "mongorestore" has replayed the dumped oplog, but it's currently impossible to do the mongorestore because the unique-index violations will abort the restore.

      We need a way to suspend unique-index constraints while restoring a dump with an oplog, then re-enable the constraints at the end of the restore. There should be a rigorous strategy in place for dealing with unique-index violations that remain at the end of the restore.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                6 Vote for this issue
                Watchers:
                19 Start watching this issue

                Dates

                • Created:
                  Updated: