-
Type: Improvement
-
Resolution: Unresolved
-
Priority: 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.
- is related to
-
SERVER-31267 CollectionCloner fails if collection is dropped between getMore calls
- Closed
-
SERVER-31695 Support read queries across collection renames
- Backlog
- tested by
-
SERVER-42606 Create test that initial sync can clone a collection while that collection is renamed
- Closed