hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ahmed Radwan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4306) Problem running Distributed Shell applications as a user other than the one started the daemons
Date Wed, 13 Jun 2012 04:26:42 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294134#comment-13294134

Ahmed Radwan commented on MAPREDUCE-4306:

Thanks Tom for the review!

I have updated the patch to handle the case you highlighted (when the current user cannot
be found and it is also not specified on the command line).

For the case of empty or null user, this will still be invalid, since the user name (picked
from ContainerLaunchContext#setUser) is used by DefaultContainerExecutor.launchContainer(..)
to construct the container directory. Basically the FileNotFoundException that was preventing
the application from running was originating from line 126: lfs.mkdir(containerDir, null,
false) because the parent directory was not correct, as it was using the wrong user in constructing
the path.

> Problem running Distributed Shell applications as a user other than the one started the
> -----------------------------------------------------------------------------------------------
>                 Key: MAPREDUCE-4306
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4306
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 2.0.0-alpha
>            Reporter: Ahmed Radwan
>            Assignee: Ahmed Radwan
>             Fix For: 2.0.1-alpha
>         Attachments: MAPREDUCE-4306.patch
> Using the tarball, if you start the yarn daemons using one user and then switch to a
different user. You can successfully run MR jobs, but DS jobs fail to run. Only able to run
DS jobs using the user who started the daemons.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message