[SERVER-29966] Add invariant that lastOpApplied doesn't change during secondary batch application Created: 03/Jul/17 Updated: 30/Oct/23 Resolved: 14/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.5, 3.7.3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Kyle Suarez |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | rollback-non-functional | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v3.6
|
||||
| Sprint: | Repl 2018-01-15, Repl 2018-02-26 | ||||
| Participants: | |||||
| Description |
|
At the end of applying a batch we move the lastOpApplied forward - right before we do that we should invariant that the lastOpApplied is still the same as what it was at the beginning of the batch, to ensure we're never setting inconsistent points as a stable timestamp candidate. |
| Comments |
| Comment by Githook User [ 16/Apr/18 ] |
|
Author: {'name': 'Kyle Suarez', 'email': 'kyle.suarez@mongodb.com', 'username': 'ksuarz'}Message: (cherry picked from commit f7c7eae48b4656ba5df0b6c6a5662fec22899d4b) Conflicts: |
| Comment by Githook User [ 14/Feb/18 ] |
|
Author: {'email': 'kyle.suarez@mongodb.com', 'name': 'Kyle Suarez', 'username': 'ksuarz'}Message: |