hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1078) Improve logging
Date Thu, 15 Mar 2007 02:59:09 GMT

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

Owen O'Malley commented on HADOOP-1078:
---------------------------------------

How do you configure log4j to print the exception and call stack? With our current configuration,
if you log like LOG.error("foo", e) you get no information from the exception, which makes
it pretty useless for debugging. *smile*

> Improve logging
> ---------------
>
>                 Key: HADOOP-1078
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1078
>             Project: Hadoop
>          Issue Type: Improvement
>            Reporter: Philippe Gassmann
>
> Loggers in hadoop are created using LogFactory.getLog("some package styled things");

> This is very confusing since the string specified in getLog() sometime is the class name
sometime not. (eg : the class org.apache.hadoop.mapred.Task contains a logger created by LogFactory.getLog("org.apache.hadoop.mapred.TaskRunner");
which is very confusing)
> I think that logger should be always created using  LogFactory.getLog(MyClass.class);
and that if a class needs a logger, then a specific logger must be crated for that class (ie:
loggers are private).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message