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

clone drop-pending collections during initial sync

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

      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:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            judah.schvimer@mongodb.com Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: