Skip to content

fix: stop replication at a durable block boundary #89

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bmuddha merged 1 commit into from
Aug 26, 2026
Merged

fix: stop replication at a durable block boundary #89

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 10 additions & 5 deletions replicator/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,14 +50,19 @@ at startup before producing their first new block, so followers clear
chain-mirrored volatile state at the same stream position while retaining
internal system accounts.

On normal follower shutdown, Control keeps consuming ordered transaction batches
until it validates the next replicated block, then barriers execution and
flushes the cursor at that boundary before stopping Ingest. The operational
block heartbeat supplies that boundary, reconnecting first when necessary.
Replication failure and snapshot restart paths do not claim this guarantee.

Ingest decodes transaction batches of at most 128 transactions and typically
128 KiB, fencing them before every block, superblock, reset, or reconnect.
A rendezvous channel assigns verification to an idle control thread; otherwise
`Ingest::flush` verifies while Control schedules earlier work. Control alone
schedules verified transactions and advances the block pacer. During the
Control-held handshake, `Ingest::stage_snapshot` may write the snapshot archive
and bootstrap durable superblock state. These roles preserve stream order
without reordering state.
Ingest verifies while Control schedules earlier work. Control alone owns
handshakes, reconnect cursors, execution barriers, snapshot staging, transaction
scheduling, and block pacing. These roles preserve stream order without a
reverse control channel.

A shared-key follower may also serve downstream followers. It derives and
validates superblock seals from replicated block boundaries and archives its own
Expand Down
Loading
Loading