HDDS-13797. Refactor OzoneManagerLock Resource class to handle hierarchical resource locking #9159
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?
Define interface HierarchicalResourceLockManager class to allow locks on resources which are hierarchical in nature where in the order of locking on such resources would be always deterministic. For instance navigating through the snapshot bucket chain or navigating through FSO tree.
Moving interface Resource and classes LeveledResource, FlatResource to a separate class to be used by HierarchicalResourceLockManager.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-13797
How was this patch tested?
Just refactoring hence no unit tests required