[
https://issues.apache.org/jira/browse/YARN-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177568#comment-14177568
]
Vinod Kumar Vavilapalli commented on YARN-2715:
-----------------------------------------------
bq. The fix for it could be similar to what we've done for YARN-2676: make the
HTTP interface anyway source hadoop.proxyuser first, then
yarn.resourcemanager.webapp.proxyuser.
This is getting complex. I propose the following:
- Have a single yarn.resourcemanager.proxyuser.* prefix
- Change both YARN RM RPC server and webapps to use the above prefix if
explictly configured. Otherwise, fall back to the common configs.
> Proxy user is problem for RPC interface if
> yarn.resourcemanager.webapp.proxyuser is not set.
> --------------------------------------------------------------------------------------------
>
> Key: YARN-2715
> URL: https://issues.apache.org/jira/browse/YARN-2715
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.6.0
> Reporter: Zhijie Shen
> Assignee: Zhijie Shen
> Priority: Blocker
>
> After YARN-2656, if people set hadoop.proxyuser for the client<-->RM RPC
> interface, it's not going to work, because ProxyUsers#sip is a singleton per
> daemon. After YARN-2656, RM has both channels that want to set this
> configuration: RPC and HTTP. RPC interface sets it first by reading
> hadoop.proxyuser, but it is overwritten by HTTP interface, who sets it to
> empty because yarn.resourcemanager.webapp.proxyuser doesn't exist.
> The fix for it could be similar to what we've done for YARN-2676: make the
> HTTP interface anyway source hadoop.proxyuser first, then
> yarn.resourcemanager.webapp.proxyuser.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
