hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Templeton (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-4353) Provide short circuit user group mapping for NM/AM
Date Sun, 15 Nov 2015 16:04:11 GMT

     [ https://issues.apache.org/jira/browse/YARN-4353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daniel Templeton updated YARN-4353:
-----------------------------------
    Attachment: YARN-4353.prelim.patch

[~vinodkv], the scope of my intentions is very limited.  I'm really only interested in the
part where the container gets launched.  See if the scope of this patch works for you.

> 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
>            Assignee: Daniel Templeton
>         Attachments: YARN-4353.prelim.patch
>
>
> 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)

Mime
View raw message