[YARN-157] The option shell_command and shell_script have conflict

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.0.1-alpha
• Component/s: applications/distributed-shell
• Labels: patch
• Target Version/s: 2.0.1-alpha, 2.0.0-alpha
• Assignee: rainy Yu
• Reporter: Li Ming
• Created: 12/Oct/12 02:11
• Updated: 05/Apr/13 03:20

Description

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.