[jira] [Commented] (YARN-2934) Improve handling of container's stderr

["Naganarasimha G R (JIRA)" <ji...@apache.org>]

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

Naganarasimha G R commented on YARN-2934:
-----------------------------------------

[~jira.shegalov],
Apologies from my side, missed to update on this jira, thanks [~nijel] for pushing me on this !
I have attached an initial version of the patch which suffices but following points are open for discussion 
# Errorfilename is sent from the application/client hence name can be any thing. Currently have used WildCard Matcher on fileName and the pattern used is "*stderr*" and also made it configurable. If the admin wants to attach multiple types then Regex matching would be required, but regex pattern is not similar to unix pattern hence for the sake of simplicity have kept Wildcard. Thoughts?
# Or other way round may be i can support as you were mentioning like, support ApplicationSubmissionContext to expose interface for clients to inform the error filename and on error use this name directly if not present then use the pattern matching. But my concern is what if the error file name mentioned as part of  interface is not matching the execution command sent !. 
# Also [~bikassaha] mentioned in his [comment|  https://issues.apache.org/jira/browse/YARN-3911?focusedCommentId=14959579&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14959579], do i need to additionally check for syslog also? if so only if the syserr doesnt exist ? and similarly what approaches would be ideal for identifying the name of the log4j file? 
# have hard coded tail size to be 4k, is it required to be configurable ?


> 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
>         Attachments: YARN-2934.v1.001.patch
>
>
> 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)