hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-10566) Refactor proxyservers out of ProxyUsers
Date Fri, 02 May 2014 22:36:20 GMT

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

Hadoop QA commented on HADOOP-10566:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12643127/HADOOP-10566.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/3903//console

This message is automatically generated.

> 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-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