[
https://issues.apache.org/jira/browse/HADOOP-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13676912#comment-13676912
]
Hudson commented on HADOOP-9593:
--------------------------------
Integrated in Hadoop-Yarn-trunk #232 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/232/])
HADOOP-9593. Changing CHANGES.txt to reflect merge to branch-2.1-beta.
(Revision 1490105)
Result = SUCCESS
acmurthy :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1490105
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
> stack trace printed at ERROR for all yarn clients without hadoop.home set
> -------------------------------------------------------------------------
>
> Key: HADOOP-9593
> URL: https://issues.apache.org/jira/browse/HADOOP-9593
> Project: Hadoop Common
> Issue Type: Bug
> Components: util
> Affects Versions: 3.0.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Fix For: 3.0.0, 2.1.0-beta
>
> Attachments: HADOOP-9593-001.patch, HADOOP-9593-002.patch
>
>
> This is the problem of HADOOP-9482 now showing up in a different application
> -one whose log4j settings haven't turned off all Shell logging.
> Unless you do that, all yarn clients will have a stack trace at error in
> their logs, which is generating false alarms and is utterly pointless. Why
> does this merit a stack trace? Why log it at error? It's not an error for a
> client app to not have these values set as long as they have the relevant
> JARs on their classpath. And if they don't, they'll get some classpath error
> instead
--
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
