[ https://issues.apache.org/jira/browse/HADOOP-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665609#comment-13665609 ]
Chris Nauroth commented on HADOOP-9593: --------------------------------------- {quote} OK, applied to trunk; it wouldn't take on branch-2. Should I create a new JIRA for that? {quote} I'd say it's not necessary. We're pretty close to merging HADOOP-8562 from trunk to branch-2, and I expect your trunk patch will apply cleanly after that. > 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 > 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