-
Type: Task
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Storage
-
None
-
Storage 2017-08-21
Currently renameCollection across databases:
- takes a global lock
- copies the data from the source collection to a temporary collection (with a different UUID) in the target database
- atomically drops the source collection and renames the temp collection in the target db to its final non-temp name in the target db.
We can change this to:
- Take a global clock
- Copy the data from the source collection to a temporary collection (with a different UUID) in the target database
- Atomically move the source collection to the drop-pending namespace, change its UUUID, rename the temp collection in the target db to its final non-temp name in the target db, and change the UUID on the dest collection to the UUID of the original source collection.
- is related to
-
SERVER-30371 Separate renameCollection across DB commands into individual oplog entries
- Closed