[ https://issues.apache.org/jira/browse/YARN-5219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15331500#comment-15331500 ]
Sunil G commented on YARN-5219: ------------------------------- Attaching error trace when an invalid shell variable is put as environment variable {noformat} 16/06/15 15:18:53 INFO mapreduce.Job: Job job_1465984116963_0001 failed with state FAILED due to: Application application_1465984116963_0001 failed 2 times due to AM Container for appattempt_1465984116963_0001_000002 exited with exitCode: 1 Failing this attempt.Diagnostics: Exception from container-launch. Container id: container_1465984116963_0001_02_000001 Exit code: 1 Exception message: /Users/sunil/local/project_home/builds/tmp/nm-local-dir/usercache/root/appcache/application_1465984116963_0001/container_1465984116963_0001_02_000001/launch_container.sh: line 5: 2: parameter null or not set Stack trace: ExitCodeException exitCode=1: /Users/sunil/local/project_home/builds/tmp/nm-local-dir/usercache/root/appcache/application_1465984116963_0001/container_1465984116963_0001_02_000001/launch_container.sh: line 5: 2: parameter null or not set at org.apache.hadoop.util.Shell.runCommand(Shell.java:946) at org.apache.hadoop.util.Shell.run(Shell.java:850) at org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:1144) at org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.launchContainer(DefaultContainerExecutor.java:238) at org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.launchContainer(ContainerLaunch.java:385) at org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:281) at org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:89) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Shell output : {noformat} > When an export var command fails in launch_container.sh, the full container > launch should fail > ---------------------------------------------------------------------------------------------- > > Key: YARN-5219 > URL: https://issues.apache.org/jira/browse/YARN-5219 > Project: Hadoop YARN > Issue Type: Bug > Reporter: Hitesh Shah > Assignee: Sunil G > Attachments: YARN-5219.001.patch > > > Today, a container fails if certain files fail to localize. However, if > certain env vars fail to get setup properly either due to bugs in the yarn > application or misconfiguration, the actual process launch still gets > triggered. This results in either confusing error messages if the process > fails to launch or worse yet the process launches but then starts behaving > wrongly if the env var is used to control some behavioral aspects. > In this scenario, the issue was reproduced by trying to do export > abc="$\{foo.bar}" which is invalid as var names cannot contain "." in bash. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org