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-10566) Refactor proxyservers out of ProxyUsers
Date Sat, 10 May 2014 22:10:45 GMT

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

Hudson commented on HADOOP-10566:
---------------------------------

FAILURE: Integrated in Hadoop-Mapreduce-trunk #1777 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1777/])
HADOOP-10566. Add toLowerCase support to auth_to_local rules for service name. (tucu) (tucu:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1593105)
* /hadoop/common/trunk/hadoop-common-project/hadoop-auth/src/main/java/org/apache/hadoop/security/authentication/util/KerberosName.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-auth/src/test/java/org/apache/hadoop/security/authentication/util/TestKerberosName.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/site/apt/SecureMode.apt.vm


> Refactor proxyservers out of ProxyUsers
> ---------------------------------------
>
>                 Key: HADOOP-10566
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10566
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: security
>    Affects Versions: 2.4.0
>            Reporter: Benoy Antony
>            Assignee: Benoy Antony
>         Attachments: HADOOP-10566.patch, HADOOP-10566.patch, HADOOP-10566.patch, HADOOP-10566.patch,
HADOOP-10566.patch
>
>
> HADOOP-10498 added proxyservers feature in ProxyUsers. It is beneficial to treat this
as a separate feature since 
> 1> The ProxyUsers is per proxyuser where as proxyservers is per cluster. The cardinality
is different. 
> 2> The ProxyUsers.authorize() and ProxyUsers.isproxyUser() are synchronized and hence
share the same lock  and impacts performance.
> Since these are two separate features, it will be an improvement to keep them separate.
It also enables one to fine-tune each feature independently.



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

Mime
View raw message