[SERVER-43025] rollback should ignore no-op startIndexBuild oplog entry Created: 23/Aug/19 Updated: 29/Oct/23 Resolved: 30/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.1 |
| Type: | Task | 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 | ||||||||||||||||||||
| Sprint: | Execution Team 2019-09-09 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Both refetch and recover to timestamp rollback algorithm should not crash on trying to rollback a no-op startIndexBuild oplog entry. |
| Comments |
| Comment by Githook User [ 30/Aug/19 ] |
|
Author: {'email': 'benety@mongodb.com', 'name': 'Benety Goh', 'username': 'benety'}Message: |