-
Notifications
You must be signed in to change notification settings - Fork 587
HDDS-11220. Initialize block length using the chunk list from DataNode before seek #7221
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
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
39d0220
HDDS-11220. Reproduction test case.
jojochuang b0f4128
Initial fix.
jojochuang 9131a6e
debug logs
jojochuang 797ccdc
Remove redundant code.
jojochuang 8ad3cbc
Fix checkstyle
jojochuang e91a155
Update per review comments.
jojochuang 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
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
@jojochuang , I think the problem we are now facing is how to make sure a reader of an open file will succeed. There are two things left last time that I'm not clearly thought about what's the right way to handle are
a. how to handle if the writer of the open file is slower than the reader of the open file. Say block A, it's block size in OM is 10 bytes, when the reader starts, the reader fetches the block A length from DN which is 80 bytes, and later, the writer writes more data, then length becomes 90 bytes, should the reader refetch the block size from DN again in this case?
b. what if there is a new block allocated by the writer?
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.
For the HBase replication case, the application expects the input stream to read until the hsync length returned by output stream before the input stream instantiates. So for your case the read shouldn't read beyond 80 bytes. And therefore, new blocks added by the writer shouldn't matter either.
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.
BTW I have applied the fix to the HBase cluster. It looks like it's working with no errors. I'm still in the process of verifying that data does get written to the destination cluster though.
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.
If HBase reader needs read to the length of output stream when reader is instantiated, then we don't have to handle the two cases mentioned above. And this patch looks good to me. Thanks @jojochuang .