-
Type:
Bug
-
Status: Closed
-
Priority:
Major - P3
-
Resolution: Fixed
-
Affects Version/s: 4.0.5, 4.1.6
-
Component/s: Storage
-
Labels:None
-
Backwards Compatibility:Fully Compatible
-
Operating System:ALL
-
Backport Requested:v4.0
-
Epic Link:
-
Sprint:Storage NYC 2018-12-31
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
-
-
SERVER-35780 `renameCollection` across databases incorrectly timestamps metadata for secondary index builds
-
- Closed
-
-
SERVER-37643 add createIndexes command logic to the index build interface
-
- Closed
-