-
Notifications
You must be signed in to change notification settings - Fork 588
HDDS-13974. Use the same gRPC steam for reading the same block. #9369
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
… offsets to be calculated correctly on the client
… on many tests to allow it to compile
…w checksum offsets to be calculated correctly on the client" This reverts commit 1f90a0a.
szetszwo
left a comment
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.
+1 the change looks good.
|
Thanks @szetszwo for the patch. A commit is missing here (#6613 (comment)). It's about releasing resources properly. Created a jira ticket for this (https://issues.apache.org/jira/browse/HDDS-14013). |
|
@chungen0126 , I have merged only up to 726f8e4 as mentioned in #6613 (comment) For further works, please wait for HDDS-13975. It is bigger change that we should merge first. Otherwise, it will keep getting conflicts. |
What changes were proposed in this pull request?
In HDDS-13973, sendCommandReadBlock(..) creates a new gRPC stream per read(..) call but not a single stream per block. If the application code uses small (e.g. 64KB) buffer, then it is going to create a lot of gRPC streams.
It should keep using the same gRPC connection for streaming a block.
Note that the code is merged from #6613 up to 726f8e4 by @sodonnel
What is the link to the Apache JIRA
HDDS-13974
How was this patch tested?
Updating existing tests