hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-10824) Refactor KMSACLs to avoid locking
Date Wed, 16 Jul 2014 13:33:09 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-10824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14063475#comment-14063475
] 

Hudson commented on HADOOP-10824:
---------------------------------

FAILURE: Integrated in Hadoop-Mapreduce-trunk #1833 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1833/])
HADOOP-10824. Refactor KMSACLs to avoid locking. (Benoy Antony via umamahesh) (umamahesh:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1610969)
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-kms/src/main/java/org/apache/hadoop/crypto/key/kms/server/KMSACLs.java


> Refactor KMSACLs to avoid locking
> ---------------------------------
>
>                 Key: HADOOP-10824
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10824
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: security
>            Reporter: Benoy Antony
>            Assignee: Benoy Antony
>             Fix For: 3.0.0
>
>         Attachments: HADOOP-10824.patch, HADOOP-10824.patch
>
>
> Currently _KMSACLs_ is made thread safe using _ReadWriteLock_. It is possible to safely
publish the _acls_ collection using _volatile_.
> Similar refactoring has been done in [HADOOP-10448|https://issues.apache.org/jira/browse/HADOOP-10448?focusedCommentId=13980112&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13980112]



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message