[
https://issues.apache.org/jira/browse/YARN-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14268712#comment-14268712
]
Gera Shegalov commented on YARN-2934:
-------------------------------------
Yes it's related, but not exclusive to AM (try
-Dmapreduce.map.env=JAVA_HOME=/no/jvm/here). It's just more severe with AM.
"cat" is not the point. Getting the real diagnostics with something is, +1 for
using tail. The pointer to the tracking page can be of little value for a busy
cluster. The RMApp is likely to age out by the time the user gets to look at
it, and there is no JHS entry because the AM crashed. It would be better to
mention the nodeAddress as well, in addition to containerId to be used with
'yarn logs'
> Improve handling of container's stderr
> ---------------------------------------
>
> Key: YARN-2934
> URL: https://issues.apache.org/jira/browse/YARN-2934
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Gera Shegalov
> Assignee: Naganarasimha G R
> Priority: Critical
>
> Most YARN applications redirect stderr to some file. That's why when
> container launch fails with {{ExitCodeException}} the message is empty.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
