[jira] [Updated] (YARN-564) Job history logs do not log anything when JVM fails to start

["Gopal V (JIRA)" <ji...@apache.org>]

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

Gopal V updated YARN-564:
-------------------------

    Attachment: yarn-error.png

Screenshot of JHS UI
                
> 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