[
https://issues.apache.org/jira/browse/HADOOP-9336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13588382#comment-13588382
]
Daryn Sharp commented on HADOOP-9336:
-------------------------------------
The semantics will be returning the UGI of the connection, so it will always
report the UGI of the original user making the connection, not of any
subsequent {{UGI.doAs}} calls. However, this jira will not universally affect
anything that doesn't explicitly use it. I intend for only the
{{FSNamesystem}} audit calls to currently use it to reduce the significant
performance bottlenecks we are encountering.
I'm contemplating filing another jira for {{UGI.doAs}} to cache a stack of
UGIs. That would greatly accelerate {{UGI.getCurrentUser}} in general.
> Allow UGI of current connection to be queried
> ---------------------------------------------
>
> Key: HADOOP-9336
> URL: https://issues.apache.org/jira/browse/HADOOP-9336
> Project: Hadoop Common
> Issue Type: Improvement
> Components: ipc
> Affects Versions: 0.23.0, 2.0.0-alpha, 3.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
>
> Querying {{UGI.getCurrentUser}} is synch'ed and inefficient for short-lived
> RPC requests. Since the connection already contains the UGI, there should be
> a means to query it directly and avoid a call to {{UGI.getCurrentUser}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
