[SERVER-45842] Remove assertion that checks whether the last applied oplog entry has the same timestamp as the requested recover timestamp in recoverFromOplogUpTo Created: 29/Jan/20 Updated: 29/Oct/23 Resolved: 29/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.4, 4.3.4 |
| Type: | Improvement | 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 | ||||||||
| Backport Requested: |
v4.2
|
||||||||
| Sprint: | Execution Team 2020-02-10 | ||||||||
| Participants: | |||||||||
| Description |
|
This was originally implemented for queryable backup, but for sharded clusters, a majority commit point is used as the recovery timestamp. Not all shards may have an oplog entry at the majority commit point, however, and the code expects an oplog entry to be there at the passed in recovery timestamp. |
| Comments |
| Comment by Githook User [ 11/Feb/20 ] |
|
Author: {'username': 'GWlodarek', 'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com'}Message: (cherry picked from commit 6c6d91edeaecd066dca7fe4479298318e7e2ca77) |
| Comment by Githook User [ 29/Jan/20 ] |
|
Author: {'username': 'GWlodarek', 'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com'}Message: |