Zhijie Shen commented on YARN-2715:

Vinod, thanks for the comments. Agree with them, and let do the filter 
refactoring in a separate Jira. Here're the response the comments related to 
this one.

bq. Test-case:

Fixed the issue of the test cases and move it into the rm submodule.

bq. AdminService should also start recognizing the new proxyuser prefix.

Refactor the code of processing RM proxy user configs, and make both RM and 
AdminService refer to it. In AdminService, make the refreshing request source 
yarn-site.xml for RM specific configs too.

bq. Add comments in RMAuthenticationFilterInitializer about why we are having 
special handling of proxy-users.

Add a comment there.

I uploaded a new patch accordingly

> 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, YARN-2715.3.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

Reply via email to