Implement the first phase of the restore algorithm where the oplog is replayed on restored collections

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      These are the next steps after SERVER-62630.

      If a timestamp was specified for a point-in-time restore, the oplog entries in local.oplog.restore will be replayed on the restored collections using the applyOps command.

      • Oplog entries for collections not restored will be skipped.
      • Oplog entries referencing a database namespace that was renamed will have to be re-written with the new database namespace before being applied.
      • An applyOps oplog entry can contain multiple oplog entries referencing multiple collections. This is how committed multi-document transactions are structured. These applyOps oplog entries will have to be re-written to remove the oplog entries referencing collections not restored before being applied.

            Assignee:
            [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            Gregory Wlodarek
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: