Loading...

XML

Word

Printable

JSON

Details

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.0.7, 4.1.7
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
Sprint:
Storage NYC 2018-12-31

Description

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~~.

Attachments

Issue Links

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

Activity

People

Assignee:: Benety Goh

Reporter:: Benety Goh

Participants:: Benety Goh, Githook User

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: Dec 21 2018 07:39:50 PM UTC

Updated:: Oct 29 2023 10:25:29 PM UTC

Resolved:: Dec 21 2018 09:44:15 PM UTC