Handle data loss error in replication read history #3704
Merged
Conversation
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
alexshtin
approved these changes
Dec 12, 2022
| err error, | ||
| ) error { | ||
| switch err.(type) { | ||
| case *serviceerror.NotFound, *serviceerror.DataLoss: |
There was a problem hiding this comment.
If the first batch of the history is lost, it will return not found.
There was a problem hiding this comment.
One assumption here is history will be there as long as mutable state is here.
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.
What changed?
Why?
We should aware of the corrupted data but also need to ability to bypass this error so it will not block the replication.
This is a clean version of #3691
How did you test it?
local test.
Potential risks
Is hotfix candidate?
No.