Skip to content

storage: harden concurrent checkpoint recovery - #18

Draft
aikins01 wants to merge 6 commits into
masterfrom
storage/concurrent-checkpoint-recovery
Draft

storage: harden concurrent checkpoint recovery#18
aikins01 wants to merge 6 commits into
masterfrom
storage/concurrent-checkpoint-recovery

Conversation

@aikins01

Copy link
Copy Markdown
Collaborator

Hardens concurrent writes and checkpoint recovery against corruption, races, and unsafe continued operation after interrupted checkpoints.

  • preserves out-of-place node, relationship, CSR, and free-space checkpoint state across failure and recovery
  • makes active/frozen WAL and shadow cleanup ordering explicit, including cleared or missing shadow recovery
  • enforces first-writer-wins catalog updates and synchronizes catalog version-chain publication
  • adds native and TSAN regressions for concurrent DDL, checkpoint failure, WAL recovery, CSR preservation, and agent-memory workloads

This remains a draft while directory-entry durability, commit/WAL failure semantics, checkpoint resource leaks, crash-injection coverage, and sticky rotated-checkpoint behavior are resolved or explicitly classified.

aikins01 added 6 commits July 10, 2026 23:25
After a durable final checkpoint marker, replay the complete shadow set under the transaction gate before cleanup. Fence the database for restart if replay or cleanup fails.
Require restart when WAL rotation or any pre-marker checkpoint phase fails after durable recovery evidence may exist. Reject queued writes before they can create an unbounded active WAL.
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.

1 participant