[
https://issues.apache.org/jira/browse/HADOOP-10566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoy Antony updated HADOOP-10566:
----------------------------------
Attachment: HADOOP-10566.patch
Attaching a patch which moves the proxyServer logic to ProxyServer. The refresh
of the ProxyServers can still be triggered via
_ProxyUsers.refreshSuperUserGroupsConfiguration_
The set of proxyservers in ProxyServers is safely published via a volatile
variable and this removes the cost of thread safety via locks (synchronized).
This is similar to the approach taken in HADOOP-10448
> 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
> Attachments: HADOOP-10566.patch
>
>
> 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 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)
