-
Notifications
You must be signed in to change notification settings - Fork 44
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.
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
Add Bifrost trim gap handling support by fast-forwarding to the latest partition snapshot #2456
Open
pcholakov
wants to merge
11
commits into
main
Choose a base branch
from
feat/trim-gap-handling
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+307
−142
Open
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
41ff6ff
Add stopped-reason to ProcessorManager root future
pcholakov c29f64f
Add trim-gap handling by fast-forwarding the partition state on startup
pcholakov 87f0c5c
Simplify open partition store logic
pcholakov ff82b72
Self-review
pcholakov c42b130
Stop reading commands from the log if a TrimGap is encountered
pcholakov 1e3ed7e
Delay startup when we have a fast-forward target we can't reach
pcholakov 49c9004
PR feedback misc
pcholakov 5611679
Model TrimGapEncountered as an error within the PP
pcholakov d75db99
add RetryPolicy todo
pcholakov 84bab4f
Rename StopReason to Error
pcholakov 2539aa3
Remove Record enum in favor of simple tuple
pcholakov File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To me, it seems more than you want to have control over the error type rather than make the runtime behave like an async task with a return value.
In that case, your PartitionProcessorStopReason becomes the error type.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe! We use
anyhow::Error
quite a bit in the PP now, so it would be difficult to disentangle the errors I care about, from other failure conditions. That aside, I still like modeling this as an outcome of either a known stop reason, or some other failure condition. I am treatingPartitionProcessorStopReason
as a normal return since both canceling the PP, or encountering a trim gap, are expected over a long enough timeline.