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

Vinod Kumar Vavilapalli commented on YARN-2715:
-----------------------------------------------

Quick comments on the patch
 - Similar to the configuration that you changed, we also need to get rid of 
RM_WEBAPP_DELEGATION_TOKEN_AUTH_FILTER (is this a compatible change?)?
 - ResourceManager.startWepApp() used to allow loading common auth-filter, we 
now require our custom filter for various reasons? /cc [~vvasudev]
 - Test-case:
    -- There's a ref to "timeline-service" in the patch
    -- No need to start the entire mini-cluster - starting RM is enough?

> 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
>         Attachments: YARN-2715.1.patch, YARN-2715.2.patch
>
>
> 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)

Reply via email to