When MigrationDestinationManager is cloning a collection with multiple indexes, the index builds are not assigned timestamps that are correct from a rollback/recovery perspective. A more detailed explanation of this issue is given in the resolved tickets SERVER-35780 and SERVER-35070.
This issue was discovered while working on SERVER-37643.
- is related to
-
SERVER-35070 multi index creates are given wrong timestamps
-
- Closed
-
-
-
- Closed
-
-
SERVER-37643 add createIndexes command logic to the index build interface
-
- Closed
-