[SERVER-64523] Move all our checkpoint'ing logic onto the same code path, so we can manage concurrent checkpoints Created: 15/Mar/22 Updated: 26/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | DM-M2, former-storex-namer, techdebt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Can find all the checkpoint calls by grepping for "->checkpoint(" to find the WT calls. The WTSessionCache::waitUntilDurable is the most sophisticated, I think, in terms of having some concurrency control attempted. |
| Comments |
| Comment by Dianna Hohensee (Inactive) [ 15/Mar/22 ] |
|
If we do have a path to do this, then there shouldn't be a need for SERVER-64507. If we can swing it. |