1. renameCollection dropTarget doesn't use dropTarget UUID
renameCollection uses the namespace of the target collection, even when an oplog entry provides the correct UUID to drop. During initial sync it is possible that the target collection (by name) in the target database is not actually the collection that was dropped, and the UUID is required. This leads to dropping the wrong collection. During oplog application with UUIDs we should always drop the UUID mentioned if provided and never drop any other UUID.
2. Rename collection with dropTarget should drop the target even if the source doesn't exist
- is duplicated by
-
SERVER-32360 Rename collection with dropTarget should drop the target even if the source doesn't exist
- Closed
- is related to
-
SERVER-33086 renameCollection target should never have identical UUID with a different database
- Closed
- related to
-
SERVER-33956 A sequence of rename and create collections that do not arrive at the correct end state
- Closed
-
SERVER-34727 Rename collection during initial sync drops extra collection
- Closed