You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Jackie Chang (JIRA)" <ji...@apache.org> on 2013/09/26 05:42:07 UTC

[jira] [Updated] (HADOOP-9995) Consistent log severity level guards and statements

     [ https://issues.apache.org/jira/browse/HADOOP-9995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jackie Chang updated HADOOP-9995:
---------------------------------

    Description: 
Developers use logs to do in-house debugging. These log statements are later demoted to less severe level and usually are guarded by their matching severity levels. However, we do see inconsistencies in trunk. A log statement like 

       if (LOG.isDebugEnabled()) {
        LOG.info("Assigned container (" + allocated + ") "

doesn't make much sense because the log statement is actually only printed out in DEBUG-level. Proposed improvements is attached.
    
> Consistent log severity level guards and statements 
> ----------------------------------------------------
>
>                 Key: HADOOP-9995
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9995
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Jackie Chang
>            Priority: Minor
>
> Developers use logs to do in-house debugging. These log statements are later demoted to less severe level and usually are guarded by their matching severity levels. However, we do see inconsistencies in trunk. A log statement like 
>        if (LOG.isDebugEnabled()) {
>         LOG.info("Assigned container (" + allocated + ") "
> doesn't make much sense because the log statement is actually only printed out in DEBUG-level. Proposed improvements is attached.

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