[
https://issues.apache.org/jira/browse/YARN-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13615271#comment-13615271
]
Hadoop QA commented on YARN-157:
--------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12575704/hadoop_yarn.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/617//console
This message is automatically generated.
> The option shell_command and shell_script have conflict
> -------------------------------------------------------
>
> Key: YARN-157
> URL: https://issues.apache.org/jira/browse/YARN-157
> Project: Hadoop YARN
> Issue Type: Bug
> Components: applications/distributed-shell
> Affects Versions: 2.0.1-alpha
> Reporter: Li Ming
> Labels: patch
> Attachments: hadoop_yarn.patch
>
>
> The DistributedShell has an option shell_script to let user specify a shell
> script which will be executed in containers. But the issue is that the
> shell_command option is a must, so if both options are set, then every
> container executor will end with exitCode=1. This is because DistributedShell
> executes the shell_command and shell_script together. For example, if
> shell_command is 'date' then the final command to be executed in container is
> "date `ExecShellScript.sh`", so the date command will treat the result of
> ExecShellScript.sh as its parameter, then there will be an error.
> To solve this, the DistributedShell should not use the value of shell_command
> option when the shell_script option is set, and the shell_command option also
> should not be mandatory.
--
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
