[
https://issues.apache.org/jira/browse/YARN-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13702568#comment-13702568
]
Jian He commented on YARN-814:
------------------------------
bq. Instead of putting string messages of where this log came from we can use
log4j L option if suitable/required.
The doc says about L option: WARNING Generating caller location information is
extremely slow and should be avoided unless execution speed is not an issue.
should we consider the speed as more of an issue over log details or vice versa?
bq. I guess it will be more helpful if we add containerId there.. (locId =
containerId)
The containerId is not directly available in this method, otherwise I need to
change the signature of the method. we probably don't want to modify the
signature just for error logging purpose.
> Difficult to diagnose a failed container launch when error due to invalid
> environment variable
> ----------------------------------------------------------------------------------------------
>
> Key: YARN-814
> URL: https://issues.apache.org/jira/browse/YARN-814
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Hitesh Shah
> Assignee: Jian He
> Attachments: YARN-814.1.patch, YARN-814.2.patch, YARN-814.3.patch,
> YARN-814.4.patch, YARN-814.patch
>
>
> The container's launch script sets up environment variables, symlinks etc.
> If there is any failure when setting up the basic context ( before the actual
> user's process is launched ), nothing is captured by the NM. This makes it
> impossible to diagnose the reason for the failure.
> To reproduce, set an env var where the value contains characters that throw
> syntax errors in bash.
--
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
