feat(inkless:consolidation): serve consolidated reads from remote via OFFSET_MOVED_TO_TIERED_STORAGE#650
Merged
Conversation
viktorsomogyi
force-pushed
the
svv/ts-unification-remote-read
branch
2 times, most recently
from
June 16, 2026 15:24
15b5030 to
e40c1b5
Compare
viktorsomogyi
changed the base branch from
svv/ts-unification-systest-test1
to
main
June 16, 2026 15:24
viktorsomogyi
force-pushed
the
svv/ts-unification-remote-read
branch
2 times, most recently
from
June 16, 2026 17:47
14a41c1 to
108581e
Compare
viktorsomogyi
marked this pull request as ready for review
June 16, 2026 18:04
viktorsomogyi
force-pushed
the
svv/ts-unification-remote-read
branch
from
June 22, 2026 10:05
108581e to
cff8f1d
Compare
… OFFSET_MOVED_TO_TIERED_STORAGE When a consolidation fetch targets an offset that sits below the diskless WAL start but at/above the whole-log start, that data was consolidated to the remote tier and can only be served from there. DisklessLeaderEndPoint now signals OFFSET_MOVED_TO_TIERED_STORAGE for that range so the stock tier-state machine rebuilds the leader-epoch cache and producer snapshot from remote before resuming the WAL fetch. This is the core read-from-remote path for consolidated topics after the diskless WAL is pruned or the local log is lost. Co-authored-by: Cursor <cursoragent@cursor.com>
viktorsomogyi
force-pushed
the
svv/ts-unification-remote-read
branch
from
June 22, 2026 10:58
cff8f1d to
51a1ede
Compare
giuseppelillo
approved these changes
Jun 22, 2026
giuseppelillo
pushed a commit
that referenced
this pull request
Jun 23, 2026
… OFFSET_MOVED_TO_TIERED_STORAGE (#650) When a consolidation fetch targets an offset that sits below the diskless WAL start but at/above the whole-log start, that data was consolidated to the remote tier and can only be served from there. DisklessLeaderEndPoint now signals OFFSET_MOVED_TO_TIERED_STORAGE for that range so the stock tier-state machine rebuilds the leader-epoch cache and producer snapshot from remote before resuming the WAL fetch. This is the core read-from-remote path for consolidated topics after the diskless WAL is pruned or the local log is lost. Co-authored-by: Cursor <cursoragent@cursor.com>
giuseppelillo
pushed a commit
that referenced
this pull request
Jun 23, 2026
… OFFSET_MOVED_TO_TIERED_STORAGE (#650) When a consolidation fetch targets an offset that sits below the diskless WAL start but at/above the whole-log start, that data was consolidated to the remote tier and can only be served from there. DisklessLeaderEndPoint now signals OFFSET_MOVED_TO_TIERED_STORAGE for that range so the stock tier-state machine rebuilds the leader-epoch cache and producer snapshot from remote before resuming the WAL fetch. This is the core read-from-remote path for consolidated topics after the diskless WAL is pruned or the local log is lost. Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When a consolidation fetch targets an offset that sits below the diskless WAL start but at/above the whole-log start, that data was consolidated to the remote tier and can only be served from there. DisklessLeaderEndPoint now signals OFFSET_MOVED_TO_TIERED_STORAGE for that range so the stock tier-state machine rebuilds the leader-epoch cache and producer snapshot from remote before resuming the WAL fetch.
This is the core read-from-remote path for consolidated topics after the diskless WAL is pruned or the local log is lost.