[ https://issues.apache.org/jira/browse/MAPREDUCE-4306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293799#comment-13293799 ]
Tom White commented on MAPREDUCE-4306: -------------------------------------- {noformat} + try { + amUser = cliParser.getOptionValue("user", UserGroupInformation + .getCurrentUser().getShortUserName()); + } catch (IOException e) { + LOG.info("Getting current user info failed" + e.getMessage()); + } {noformat} If a user has been specified on the command line then there is no need to find the current user. In fact, if the current user can't be found then {{amUser}} won't be set. (Also, there's a space missing in the info line.) It's probably worth going through where user values are null or the empty string to check they are correct (e.g. on ContainerLaunchContext#setUser). > Problem running Distributed Shell applications as a user other than the one > started the daemons > ----------------------------------------------------------------------------------------------- > > 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