HDDS-6047. [Ozone-Streaming] Support merge chunkInfos in client. #2870
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
|
This is useful and saves rocksdb a lot of space in the Container |
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 changes were proposed in this pull request?
The chunk size of the streaming is usually smaller than 4MB, we suggest set to 512KB for better performance. In this case, files of the same size will generate more chunkInfo than async write, which increases the size of container DB. So we recommend add merge on the client side. The default value is 0, means merge is not enabled. If the value is 8, it means that every 8 chunkInfo will be merged to one.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-6047
How was this patch tested?
UT added.