You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Benoy Antony (JIRA)" <ji...@apache.org> on 2014/05/02 08:29:25 UTC

[jira] [Updated] (HADOOP-10566) Refactor proxyservers out of ProxyUsers

     [ https://issues.apache.org/jira/browse/HADOOP-10566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benoy Antony updated HADOOP-10566:
----------------------------------

    Description: 
HADOOP-10498 added proxyserversfeature 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 ProxyUser.authorize() and 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.


  was:
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 ProxyUser.authorize() and 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.



> Refactor proxyservers out of ProxyUsers
> ---------------------------------------
>
>                 Key: HADOOP-10566
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10566
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: security
>            Reporter: Benoy Antony
>            Assignee: Benoy Antony
>
> HADOOP-10498 added proxyserversfeature 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 ProxyUser.authorize() and 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)