-
Notifications
You must be signed in to change notification settings - Fork 588
HDDS-9387. [hsync] Reduce updating block length times at OM during hsync #6054
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
Conversation
| } else { | ||
| omClient.hsyncKey(keyArgs, openID); | ||
| if (keyArgs.getLocationInfoList().size() == 0) { | ||
| omClient.hsyncKey(keyArgs, openID); |
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.
Why do we want to hsync without any block info? Or can we return error in this case.
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.
hsync is called right after file is created. See TestHSync#testUncommittedBlocks.
...d-rocksdb/src/main/java/org/apache/hadoop/hdds/utils/db/managed/ManagedRocksObjectUtils.java
Outdated
Show resolved
Hide resolved
hadoop-ozone/integration-test/src/test/java/org/apache/hadoop/fs/ozone/TestHSync.java
Show resolved
Hide resolved
...ozone/client/src/main/java/org/apache/hadoop/ozone/client/io/BlockOutputStreamEntryPool.java
Show resolved
Hide resolved
|
Thanks Sammi and Ashish! |
What changes were proposed in this pull request?
Update block length at OM per block when hsync is called.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-9387
How was this patch tested?
new unit tests