[SERVER-85722] Investigate assumption that mongo layer always tells storage engine when to take a checkpoint Created: 25/Jan/24 Updated: 02/Feb/24 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 8.0 Required |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Samyukta Lanka | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | repl-shortlist | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
The mongo layer implicitly has an assumption that it always initiates all checkpoints in the storage engine. However, there are several situations where WT might internally take a checkpoint (the most recent one being background compaction) without the mongo layer being aware, which means that this assumption is not correct. We should investigate whether there are areas that are relying on this assumption, especially if they could affect correctness of the system. |