hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9593) stack trace printed at ERROR for all yarn clients without hadoop.home set
Date Thu, 23 May 2013 18:31:20 GMT

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

Chris Nauroth commented on HADOOP-9593:
---------------------------------------

+1 for the patch.  Thanks, Steve.  Downgrading to debug level sounds like a helpful first
step.

{code}
+        LOG.debug("setsid exited with exit code "
+                  + (shexec != null ? shexec.getExitCode() : "(null executor"));
{code}

Really minor nitpick: did you intend to have a closing paren inside the string literal for
"(null executor" ?

                
> 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
>
>
> 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

Mime
View raw message