-
Notifications
You must be signed in to change notification settings - Fork 23
CASSANALYTICS-129 : Fix ReadStatusTracker to distinguish clean completion from error termination in BufferingCommitLogReader #182
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
Open
jyothsnakonisa
wants to merge
1
commit into
apache:trunk
Choose a base branch
from
jyothsnakonisa:ninja-commitlog-reader
base: trunk
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.
Open
Changes from all commits
Commits
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 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
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
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.
So my understanding of this is that we have both:
a. a path that can terminate gracefully with the
LEGACY_END_OF_SEGMENT_MARKER, andb. a path that terminates gracefully when our idx file says we're completed and we trust it
We have an issue where above in the code we have if we're < 4 bytes from the end of a segment on a legacy CommitLog - this isn't an error case at all but if we find it, we flag
statusTrackerto error:So in this case, we'll
requestTerminationon the statusTracker which sets:That'll then run afoul of the logic you have here, since the
statusTracker.shouldContinue()will return false and thus we not set position to log.maxOffset. Overloading thestatusTracker.requestTerminationto mean both "things are fine" and "things are failed" is making this incorrect I think.If we augment
ReadStatusTrackerto have both amarkAsError()method that setserror = true;and a separatemarkCleanCompletion()that sets another boolean, we'll cleanly work around this situation and can check the combination of:if (log.completed() && statusTracker.noErrors() && statusTracker.isCompleted())(or whatever better names you'd pick), then I think we'd be solid here and be able to handle both the legacy CDC path and the new index based.