smengcl commented on a change in pull request #2734:
URL: https://github.com/apache/ozone/pull/2734#discussion_r734751100
##########
File path:
hadoop-ozone/common/src/main/java/org/apache/hadoop/ozone/om/lock/OzoneManagerLock.java
##########
@@ -390,6 +390,7 @@ private void unlock(Resource resource, String resourceName,
S3_SECRET_LOCK((byte) 4, "S3_SECRET_LOCK"), // 31
PREFIX_LOCK((byte) 5, "PREFIX_LOCK"); //63
+// TENANT_LOCK((byte) 6, "TENANT_LOCK"); // 127
Review comment:
This is not implemented now. Pending discussion. I feel like the current
tenant logic depends on `VOLUME_LOCK` where it isn't necessary, for example in
AssignUser Ratis request. If we have `TENANT_LOCK` we can have finer
granularity lock than what we use currently.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
