Skip to content

WAL checkpointing: Explicitly checkpoint after common/large writes#90

Merged
OpsBotPrime merged 2 commits intomasterfrom
wal-explicit_checkpointing_after_writes
Apr 28, 2026
Merged

WAL checkpointing: Explicitly checkpoint after common/large writes#90
OpsBotPrime merged 2 commits intomasterfrom
wal-explicit_checkpointing_after_writes

Conversation

@Qqwy
Copy link
Copy Markdown
Contributor

@Qqwy Qqwy commented Apr 1, 2026

Follow-up of #89

  • Ensures we use the periodic checkpointing time interval in Skip mode rather than Burst
  • Always checkpoint after inserting a new submission. This is a protection against the situations in which submissions with many thousands of chunks are added, which is the failure we saw today.
  • Checkpoint every 100 chunks that are completed.

The last two situations already have a write connection at the time they get to running the checkpoint query, which will make checkpoint-starvation (which in all likelihood is what we saw before) improbable.

@Qqwy Qqwy force-pushed the wal-explicit_checkpointing_after_writes branch from 2198571 to 8b2ed04 Compare April 28, 2026 08:43
@Qqwy
Copy link
Copy Markdown
Contributor Author

Qqwy commented Apr 28, 2026

@OpsBotPrime merge and tag

@OpsBotPrime
Copy link
Copy Markdown
Contributor

Rebased as 7915a18, waiting for CI …

@OpsBotPrime
Copy link
Copy Markdown
Contributor

CI job 🟡 started.

@OpsBotPrime OpsBotPrime force-pushed the wal-explicit_checkpointing_after_writes branch from a77b10a to 7915a18 Compare April 28, 2026 09:55
@OpsBotPrime
Copy link
Copy Markdown
Contributor

@Qqwy I tagged your PR with v50. Please wait for the build of 7915a18 to pass and don't forget to deploy it!

@OpsBotPrime OpsBotPrime merged commit 7915a18 into master Apr 28, 2026
6 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants