You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "rainy Yu (JIRA)" <ji...@apache.org> on 2013/04/05 05:22:16 UTC

[jira] [Updated] (YARN-157) The option shell_command and shell_script have conflict

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

rainy Yu updated YARN-157:
--------------------------

    Attachment: shell_script.sh
                YARN-157.patch

Add unit test. Thank Vinod Kumar Vavilapalli for help
                
> 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
>            Assignee: rainy Yu
>              Labels: patch
>         Attachments: hadoop_yarn.patch, shell_script.sh, YARN-157.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