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

Recoverable Rollback: Support rolling back of dropCollection oplog entries using collection UUIDs.

    • Type: Icon: Task Task
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Replication
    • Fully Compatible

      The existing rollback implementation in 3.4 requires the entire collection to be copied from the sync source when rolling back a dropCollections command. With the introduction of Collection UUIDs in 3.6 and 2-phase drops in 3.6, this should no longer be necessary. We can recover the dropped collection by fixing up the Namespace to UUID links in the collection catalog.

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            benety.goh@mongodb.com Benety Goh
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: