HDDS-7107. Determine OzoneManagerStateMachine multipleExecutors index via hashing #3664
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
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?
[To be merged after HDDS-7105 PR #3662] Introduce an interface
OMHashCodeGeneratorwhich translates each of theOBJECT_STORE "OBS"bucket layout key path names into a hash code based on the corresponding hash function used.The write operations on different key paths now have their corresponding hash codes and are allotted a thread writer (executor) index for execution determined via the modulo (
hashCode % om.num.concurrent.write.threads) - this enables concurrency for write operations.Please refer link.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-7107
How was this patch tested?
Added integration tests