[ 
https://issues.apache.org/jira/browse/YARN-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14268767#comment-14268767
 ] 

Gera Shegalov commented on YARN-2934:
-------------------------------------

bq. Given this, even the tailed stderr is not useful in such a situation. If 
the app-page ages out, where will the user see this additional diagnostic 
message that we tail out of logs?

It will be in the client output that I showed in the above comments. In our 
infrastructure, a failed job will generate an alert email containing the client 
log (or link to it).


> 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)

Reply via email to