-
Notifications
You must be signed in to change notification settings - Fork 3.4k
HBASE-30352: Tolerate stale recovered.edits below durable seqid in split/merge #8599
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
nirdosh0110
wants to merge
4
commits into
apache:master
Choose a base branch
from
nirdosh0110:drop-stale-recovered-edits
base: master
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.
+135
−3
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
6f01342
HBASE-XXXXX Tolerate stale recovered.edits below durable seqid in spl…
c7e4623
HBASE-30352 Address review: reframe comment; drop dead parseLong guard
ea9fc7d
Handling NumberFormatException while parsing long value
nirdosh0110 0fc64bf
HBASE-30352 Fix spotless line-length violation in NumberFormatExcepti…
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.
We can get this value by reading all the HFiles' metadata?
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.
Good point. The reason for going with
ServerManagerhere was consistency — SCP consults the same map when deciding what entersrecovered.editsin the first place, so both decisions come from one source and cannot disagree. That said, HFile metadata is stronger: it is the on-disk truth and would decouple this check from HBASE-30335's seed timing (and from a coldServerManagercache right after master restart).Reading it correctly means
min across families of max HFile seqid(the same fenceHRegion.replayRecoveredEditsIfAnyuses when skipping already-flushed edits). Roughly:HRegionFileSystem.openRegionFromFileSystem→ per familyStoreFileTracker.load()→ wrap eachStoreFileInfoinHStoreFilewithCacheConfig.DISABLED→getReader().getSequenceID(). Same patternMergeTableRegionsProcedure.mergeStoreFilesalready uses in this package.Would you prefer I switch entirely to the HFile-metadata source in this PR, or keep
ServerManagerprimary with HFile-metadata as a fallback when the cache is empty? Happy to do either.