[SERVER-53946] Resume batching from the last noop entry even if it is less than the startApplyingDonorOpTime Created: 21/Jan/21 Updated: 29/Oct/23 Resolved: 09/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Lingzhi Deng | Assignee: | Jason Chan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm-1791_milestone-H | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Repl 2021-03-08, Repl 2021-03-22 | ||||||||
| Participants: | |||||||||
| Description |
|
Currently, the tenant oplog batcher restarts from scratch if the last noop entry we find in the oplog is less than startApplyingDonorOpTime. |
| Comments |
| Comment by Githook User [ 09/Mar/21 ] |
|
Author: {'name': 'Jason Chan', 'email': 'jason.chan@mongodb.com', 'username': 'jasonjhchan'}Message: |