[
https://issues.apache.org/jira/browse/HDDS-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16872808#comment-16872808
]
Hudson commented on HDDS-1727:
------------------------------
FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #16824 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/16824/])
HDDS-1727. Use generation of resourceName for locks in OzoneManagerLock.
(github: rev a79bdf760e31f2ee3d707ca88eec92fbf70198c0)
* (edit)
hadoop-hdds/common/src/main/java/org/apache/hadoop/ozone/OzoneConsts.java
* (edit)
hadoop-ozone/common/src/main/java/org/apache/hadoop/ozone/om/lock/OzoneManagerLockUtil.java
* (edit)
hadoop-ozone/common/src/test/java/org/apache/hadoop/ozone/om/lock/TestOzoneManagerLock.java
* (edit)
hadoop-ozone/common/src/main/java/org/apache/hadoop/ozone/om/lock/OzoneManagerLock.java
> Use generation of resourceName for locks in OzoneManagerLock
> ------------------------------------------------------------
>
> Key: HDDS-1727
> URL: https://issues.apache.org/jira/browse/HDDS-1727
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Bharat Viswanadham
> Assignee: Bharat Viswanadham
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.4.1
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> In this Jira, we shall use generate Resourcename from actual resource names
> like volume/bucket/user/key inside OzoneManagerLock. In this way, users using
> these locking API's no need to worry of calling these additional API of
> generateResourceName in OzoneManagerLockUtil. And this also reduces code
> during acquiring locks in OM operations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
