[SERVER-38745] MigrationDestinationManager assigns incorrect timestamps while building multiple indexes Created: 21/Dec/18 Updated: 29/Oct/23 Resolved: 21/Dec/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 4.0.5, 4.1.6 |
| Fix Version/s: | 4.0.7, 4.1.7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Benety Goh |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Backport Requested: |
v4.0
|
||||||||||||||||||||
| Sprint: | Storage NYC 2018-12-31 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| 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 This issue was discovered while working on |
| Comments |
| Comment by Githook User [ 09/Mar/19 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: (cherry picked from commit 7b85fb049b087fbcb04d6f356a0f7bee9ef48190) |
| Comment by Githook User [ 21/Dec/18 ] |
|
Author: {'username': 'benety', 'email': 'benety@mongodb.com', 'name': 'Benety Goh'}Message: |