clone drop-pending collections during initial sync

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Replication
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Since we don't clone them, if we roll back the collection drop, the rollback will fail. This leads to an fassert during rollback, not data corruption.

      When fixed, we need to make sure that we register the drop pending collection with the reaper so that it gets reaped at the appropriate optime.

            Assignee:
            [DO NOT USE] Backlog - Replication Team
            Reporter:
            Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: