[SERVER-45839] recoverFromOplogUpTo should not invariant if there are no oplog entries to apply between the given range Created: 29/Jan/20 Updated: 29/Oct/23 Resolved: 30/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.4, 4.3.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Wlodarek | Assignee: | Gregory Wlodarek |
| 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.2
|
||||||||||||
| Sprint: | Execution Team 2020-02-10 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
recoverFromOplogUpTo was added as part of the queryable project and after integration testing with cloud backup, we missed an edge case where there are no oplog entries to apply between the given range, but the oplog entry at the start point is present, which we skip. Because of that, later on, we try to set the applied through point to the null timestamp causing an invariant. |
| Comments |
| Comment by Githook User [ 11/Feb/20 ] |
|
Author: {'username': 'GWlodarek', 'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com'}Message: (cherry picked from commit d422e688b9e4b7a933dcafdd779f8f957dc357ab) |
| Comment by Githook User [ 11/Feb/20 ] |
|
Author: {'username': 'GWlodarek', 'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com'}Message: (cherry picked from commit 4bea6f38267b33731f4f95e4fb10396bc6f9c8b5) |
| Comment by Githook User [ 30/Jan/20 ] |
|
Author: {'name': 'Gregory Wlodarek', 'username': 'GWlodarek', 'email': 'gregory.wlodarek@mongodb.com'}Message: |
| Comment by Githook User [ 30/Jan/20 ] |
|
Author: {'username': 'GWlodarek', 'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com'}Message: |