hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandy Ryza (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1100) Giving multiple commands to ContainerLaunchContext doesn't work as expected
Date Tue, 03 Sep 2013 17:17:52 GMT

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

Sandy Ryza commented on YARN-1100:

In the MR and distributed shell code, the command list does not seem to be used for holding
arguments to the same process.  All arguments are concatenated and placed in a single entry
in the commands list.
> Giving multiple commands to ContainerLaunchContext doesn't work as expected
> ---------------------------------------------------------------------------
>                 Key: YARN-1100
>                 URL: https://issues.apache.org/jira/browse/YARN-1100
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: api, nodemanager
>    Affects Versions: 2.1.0-beta
>            Reporter: Sandy Ryza
> A ContainerLaunchContext accepts a list of commands (as strings) to be executed to launch
the container.  I would expect that giving a list with the two commands "echo yolo" and "date"
would print something like
> {code}
> yolo
> Mon Aug 26 14:40:23 PDT 2013
> {code}
> Instead it prints
> {code}
> yolo date
> {code}
> This is because the commands get executed with:
> {code}
> exec /bin/bash -c "echo yolo date"
> {code}
> To get the expected behavior I have to include semicolons at the end of each command.
At the very least, this should be documented, but I think better would be for the NM to insert
the semicolons.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message