You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Daniel Templeton (JIRA)" <ji...@apache.org> on 2015/11/12 22:55:10 UTC

[jira] [Commented] (YARN-4353) Provide short circuit user group mapping for NM/AM

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

Daniel Templeton commented on YARN-4353:
----------------------------------------

Looks like I don't have permission to assign this to myself yet...  In the meantime, I'm working on a patch.

> Provide short circuit user group mapping for NM/AM
> --------------------------------------------------
>
>                 Key: YARN-4353
>                 URL: https://issues.apache.org/jira/browse/YARN-4353
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager
>    Affects Versions: 2.7.1
>            Reporter: Daniel Templeton
>
> When the NM launches an AM, the {{ContainerLocalizer}} gets the current user from {{UserGroupInformation}}, which triggers user group mapping, even though the user groups are never accessed.  If secure LDAP is configured for group mapping, then there are some additional complications created by the unnecessary group resolution.  Additionally, it adds unnecessary latency to the container launch time.
> To address the issue, before getting the current user, the {{ContainerLocalizer}} should configure {{UserGroupInformation}} with a null group mapping service that quickly and quietly returns an empty group list for all users.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)