hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remus Rusanu (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (YARN-2485) Fix WSCE folder/file/classpathJar permission/order when running as non-admin
Date Mon, 15 Sep 2014 13:35:33 GMT

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

Remus Rusanu resolved YARN-2485.
    Resolution: Duplicate

This is fixed by YARN-2458 implementation of a en 'elevated' file system for WSCE.

> Fix WSCE folder/file/classpathJar permission/order when running as non-admin
> ----------------------------------------------------------------------------
>                 Key: YARN-2485
>                 URL: https://issues.apache.org/jira/browse/YARN-2485
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager
>            Reporter: Remus Rusanu
>            Assignee: Remus Rusanu
>              Labels: security, windows
> The WSCE creates the local, usercache, filecache appcache dirs in the normal DefaultContainerExecutor
way, and then assigns ownership to the userprocess. The WSCE configured group is added, but
the permission masks used (710) do no give write permissions on the appcache/filecache/usercache
folder to the NM itself.
> The creation of these folders, as well as the creation of the temporary classPath jar
files must succeed even after thes file/dir ownership is relinquished to the task user and
the NM does not run as a local Administrator. 
> LCE handles all these dirs inside the container-executor app (root). The classpathJar
issue does not exists on Linux.
> The dirs can be handled by simply delaying the transfer (create all dirs and temp files,
then assign ownership in bulk) but the task classpathJar is 'special' and needs some refactoring
of the NM launch sequence.

This message was sent by Atlassian JIRA

View raw message