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

Support rename collections during initial sync by retrying

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Replication
    • 63

      If a collection is renamed during initial sync, the getMore will return an error (either CursorNotFound or OperationFailed). We can detect that this is due to a rename doing a find by UUID; if the find is successful the response contains the new name. If we respond to this by re-starting the clone and persisting it locally to the old name, initial sync will work correctly with the rename being applied later during oplog application.

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            matthew.russotto@mongodb.com Matthew Russotto
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: