HDDS-10874. Create non-caching XceiverClientFactory implementation #7044
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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?
DNRPCLoadGeneratorhas a--clientsparameter to specify the number of client objects. Supposedly clients can issue requests to datanodes in parallel, but becauseXceiverClientManagercaches clients, only one client is ever instantiated.This change fixes that by adding a non-caching implementation
XceiverClientCreator, as the parent class ofXceiverClientManager. Freon can now use it to avoid the bottleneck due to single client.https://issues.apache.org/jira/browse/HDDS-10874
How was this patch tested?
CI:
https://github.com/adoroszlai/ozone/actions/runs/10282922004