[SERVER-79234] Revisit allDurable and lastApplied check before truncation of pre-images Created: 24/Jul/23 Updated: 26/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Haley Connelly | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | oldstorexemea, techdebt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||
| Participants: | |||||||||
| Description |
|
Right now, the allDurable and lastApplied timestamps are computed once, and used as a barrier to protect against truncating pre-images that are not yet part of a consistent range of data (due to oplog holes/ secondary oplog application). We should reconsider placing the check in _hasExcessMarkers so pre-images are not considered 'excess' from the start, rather than waiting to do the check before truncation. |