[
https://issues.apache.org/jira/browse/YARN-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718642#comment-13718642
]
Jian He commented on YARN-564:
------------------------------
This was fixed along with YARN-814
reproduced as mentioned above, I can see log from both NM and web UI as:
{code}
Exception from container-launch:
org.apache.hadoop.util.Shell$ExitCodeException:
/tmp/hadoop-jhe/nm-local-dir/usercache/jhe/appcache/application_1374688495663_0001/container_1374688495663_0001_01_000004/launch_container.sh:
line 30: unexpected EOF while looking for matching `"'
/tmp/hadoop-jhe/nm-local-dir/usercache/jhe/appcache/application_1374688495663_0001/container_1374688495663_0001_01_000004/launch_container.sh:
line 31: syntax error: unexpected end of file
at org.apache.hadoop.util.Shell.runCommand(Shell.java:458)
at org.apache.hadoop.util.Shell.run(Shell.java:373)
at
org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:578)
at
org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.launchContainer(DefaultContainerExecutor.java:195)
at
org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:258)
at
org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:74)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:680)
{code}
> Job history logs do not log anything when JVM fails to start
> ------------------------------------------------------------
>
> Key: YARN-564
> URL: https://issues.apache.org/jira/browse/YARN-564
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 3.0.0
> Environment: Ubuntu 64bit
> Reporter: Gopal V
> Priority: Minor
> Labels: usability
> Attachments: yarn-error.png
>
>
> If the -Xmx line in a java invocation has errors such as is possible with
> quoting issues as would be possible with hive
> hive> set mapred.map.child.java.opts="-server -Xmx2248m
> -Djava.net.preferIPv4Stack=true";
> The diagnostic error message says
> {code}
> FAILED: Execution Error, return code 2 from
> org.apache.hadoop.hive.ql.exec.MapRedTask
> {code}
> The job history UI is rather unhelpful and the UI says
> {code}
> Attmpt state missing from History : marked as KILLED
> {code}
> And the log files are not available and instead show
> {code}
> Logs not available for attempt_1365673149565_0002_m_000000_3. Aggregation may
> not be complete, Check back later or try the nodemanager at :-1
> {code}
--
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
