[
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 levels 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 message is actually only printed out in
DEBUG-level. We do see previous issues tried to correct this inconsistency. I
am proposing a comprehensive correction over trunk.
HDFS-1611 also corrected this inconsistency.
was:
Developers use logs to do in-house debugging. These log statements are later
demoted to less severe levels 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 message is actually only printed out in
DEBUG-level. We do see previous issues tried to correct this inconsistency. I
am proposing a comprehensive correction over trunk.
> 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
> Attachments: HADOOP-9995.patch
>
>
> Developers use logs to do in-house debugging. These log statements are later
> demoted to less severe levels 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 message is actually only printed out
> in DEBUG-level. We do see previous issues tried to correct this
> inconsistency. I am proposing a comprehensive correction over trunk.
> HDFS-1611 also corrected this inconsistency.
--
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
