You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2013/05/23 19:17:21 UTC

[jira] [Created] (HADOOP-9593) stack trace printed at ERROR for all yarn clients without hadoop.home set

Steve Loughran created HADOOP-9593:
--------------------------------------

             Summary: 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
            Reporter: Steve Loughran


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