hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2851) Bogus logging messages in Configration object constructors
Date Tue, 15 Apr 2008 16:51:05 GMT

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

Steve Loughran commented on HADOOP-2851:
----------------------------------------

looks like someone wants a way to get a stack trace of wherever a configuration is created.
Sometimes that could be useful. As it is only done if the debug log is enabled, its cost is
otherwise minimal. 

Recommend leaving as is, file as INVALID or WONTFIX.


> Bogus logging messages in Configration object constructors
> ----------------------------------------------------------
>
>                 Key: HADOOP-2851
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2851
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: conf
>    Affects Versions: 0.16.0
>            Reporter: Jingkei Ly
>            Priority: Trivial
>
> The constructors for the Configuration object contains a superfluous logging message
that logs an IOException whenever logging is enabled for the debug level. Basically both constructors
have the statement:
> if (LOG.isDebugEnabled()) {
>       LOG.debug(StringUtils.stringifyException(new IOException("config()")));
>     }
> I can' t see any reason for it to be there and it just ends up leaving bogus IOExceptions
in log files. It looks like its an old debug print statement which has accidentally been left
in.

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