[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
]
Jagadesh Kiran N updated HADOOP-9995:
-
Attachment: HADOOP-9995-00.patch
Hi [~kanaka] ,as discussed i have assigned the same to me, Uploaded the patch
on latest trunk code base.
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
Assignee: Jagadesh Kiran N
Priority: Minor
Labels: BB2015-05-TBR
Attachments: HADOOP-9995-00.patch, 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
{code}
if (LOG.isDebugEnabled()) {
LOG.info(Assigned container ( + allocated + )
{code}
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.
Doug Cutting pointed it out in HADOOP-312:
https://issues.apache.org/jira/browse/HADOOP-312?focusedCommentId=12429498page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12429498
HDFS-1611 also corrected this inconsistency.
This could have been avoided by switching from log4j to slf4j's {} format
like CASSANDRA-625 (2010/3) and ZOOKEEPER-850 (2012/1), which gives cleaner
code and slightly higher performance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[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
]
Jagadesh Kiran N updated HADOOP-9995:
-
Status: Patch Available (was: Open)
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
Assignee: Jagadesh Kiran N
Priority: Minor
Labels: BB2015-05-TBR
Attachments: HADOOP-9995-00.patch, 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
{code}
if (LOG.isDebugEnabled()) {
LOG.info(Assigned container ( + allocated + )
{code}
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.
Doug Cutting pointed it out in HADOOP-312:
https://issues.apache.org/jira/browse/HADOOP-312?focusedCommentId=12429498page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12429498
HDFS-1611 also corrected this inconsistency.
This could have been avoided by switching from log4j to slf4j's {} format
like CASSANDRA-625 (2010/3) and ZOOKEEPER-850 (2012/1), which gives cleaner
code and slightly higher performance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[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
]
kanaka kumar avvaru updated HADOOP-9995:
Target Version/s: (was: 2.1.1-beta)
Status: Open (was: Patch Available)
Planning to upload patch on latest trunk code base as the current patch file is
too old.
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
Assignee: kanaka kumar avvaru
Priority: Minor
Labels: BB2015-05-TBR
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
{code}
if (LOG.isDebugEnabled()) {
LOG.info(Assigned container ( + allocated + )
{code}
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.
Doug Cutting pointed it out in HADOOP-312:
https://issues.apache.org/jira/browse/HADOOP-312?focusedCommentId=12429498page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12429498
HDFS-1611 also corrected this inconsistency.
This could have been avoided by switching from log4j to slf4j's {} format
like CASSANDRA-625 (2010/3) and ZOOKEEPER-850 (2012/1), which gives cleaner
code and slightly higher performance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[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
]
Allen Wittenauer updated HADOOP-9995:
-
Labels: BB2015-05-TBR (was: )
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
Labels: BB2015-05-TBR
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
{code}
if (LOG.isDebugEnabled()) {
LOG.info(Assigned container ( + allocated + )
{code}
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.
Doug Cutting pointed it out in HADOOP-312:
https://issues.apache.org/jira/browse/HADOOP-312?focusedCommentId=12429498page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12429498
HDFS-1611 also corrected this inconsistency.
This could have been avoided by switching from log4j to slf4j's {} format
like CASSANDRA-625 (2010/3) and ZOOKEEPER-850 (2012/1), which gives cleaner
code and slightly higher performance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[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:
-
Status: Patch Available (was: Open)
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
{code}
if (LOG.isDebugEnabled()) {
LOG.info(Assigned container ( + allocated + )
{code}
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.
Doug Cutting pointed it out in HADOOP-312:
https://issues.apache.org/jira/browse/HADOOP-312?focusedCommentId=12429498page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12429498
HDFS-1611 also corrected this inconsistency.
This could have been avoided by switching from log4j to slf4j's {} format
like CASSANDRA-625 (2010/3) and ZOOKEEPER-850 (2012/1), which gives cleaner
code and slightly higher performance.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[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 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
[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 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.
Doug Cutting pointed it out in HADOOP-312:
https://issues.apache.org/jira/browse/HADOOP-312?focusedCommentId=12429498page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12429498
HDFS-1611 also corrected this inconsistency.
This could have been avoid by switching from log4j to slf4j like CASSANDRA-625
(2010/3) and ZOOKEEPER-850 (2012/1).
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.
HDFS-1611 also corrected this inconsistency.
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.
Doug Cutting pointed it out in HADOOP-312:
https://issues.apache.org/jira/browse/HADOOP-312?focusedCommentId=12429498page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12429498
HDFS-1611 also corrected this inconsistency.
This could have been avoid by switching from log4j to slf4j like
CASSANDRA-625 (2010/3) and ZOOKEEPER-850 (2012/1).
--
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
[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 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.
Doug Cutting pointed it out in HADOOP-312:
https://issues.apache.org/jira/browse/HADOOP-312?focusedCommentId=12429498page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12429498
HDFS-1611 also corrected this inconsistency.
This could have been avoided by switching from log4j to slf4j like
CASSANDRA-625 (2010/3) and ZOOKEEPER-850 (2012/1).
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.
Doug Cutting pointed it out in HADOOP-312:
https://issues.apache.org/jira/browse/HADOOP-312?focusedCommentId=12429498page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12429498
HDFS-1611 also corrected this inconsistency.
This could have been avoid by switching from log4j to slf4j like CASSANDRA-625
(2010/3) and ZOOKEEPER-850 (2012/1).
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.
Doug Cutting pointed it out in HADOOP-312:
https://issues.apache.org/jira/browse/HADOOP-312?focusedCommentId=12429498page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12429498
HDFS-1611 also corrected this inconsistency.
This could have been avoided by switching from log4j to slf4j like
CASSANDRA-625 (2010/3) and ZOOKEEPER-850 (2012/1).
--
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
[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 levels and usually are guarded by their matching
severity levels. However, we do see inconsistencies in trunk. A log statement
like
{code}
if (LOG.isDebugEnabled()) {
LOG.info(Assigned container ( + allocated + )
{code}
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.
Doug Cutting pointed it out in HADOOP-312:
https://issues.apache.org/jira/browse/HADOOP-312?focusedCommentId=12429498page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12429498
HDFS-1611 also corrected this inconsistency.
This could have been avoided by switching from log4j to slf4j's {} format like
CASSANDRA-625 (2010/3) and ZOOKEEPER-850 (2012/1), which gives cleaner code and
slightly higher performance.
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
{code}
if (LOG.isDebugEnabled()) {
LOG.info(Assigned container ( + allocated + )
{code}
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.
Doug Cutting pointed it out in HADOOP-312:
https://issues.apache.org/jira/browse/HADOOP-312?focusedCommentId=12429498page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12429498
HDFS-1611 also corrected this inconsistency.
This could have been avoided by switching from log4j to slf4j like
CASSANDRA-625 (2010/3) and ZOOKEEPER-850 (2012/1).
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
{code}
if (LOG.isDebugEnabled()) {
LOG.info(Assigned container ( + allocated + )
{code}
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.
Doug Cutting pointed it out in HADOOP-312:
https://issues.apache.org/jira/browse/HADOOP-312?focusedCommentId=12429498page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12429498
HDFS-1611 also corrected this inconsistency.
This could have been avoided by switching from log4j to slf4j's {} format
like CASSANDRA-625 (2010/3) and ZOOKEEPER-850 (2012/1), which gives cleaner
code and slightly higher performance.
--
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
[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 levels and usually are guarded by their matching
severity levels. However, we do see inconsistencies in trunk. A log statement
like
{code}
if (LOG.isDebugEnabled()) {
LOG.info(Assigned container ( + allocated + )
{code}
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.
Doug Cutting pointed it out in HADOOP-312:
https://issues.apache.org/jira/browse/HADOOP-312?focusedCommentId=12429498page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12429498
HDFS-1611 also corrected this inconsistency.
This could have been avoided by switching from log4j to slf4j like
CASSANDRA-625 (2010/3) and ZOOKEEPER-850 (2012/1).
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.
Doug Cutting pointed it out in HADOOP-312:
https://issues.apache.org/jira/browse/HADOOP-312?focusedCommentId=12429498page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12429498
HDFS-1611 also corrected this inconsistency.
This could have been avoided by switching from log4j to slf4j like
CASSANDRA-625 (2010/3) and ZOOKEEPER-850 (2012/1).
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
{code}
if (LOG.isDebugEnabled()) {
LOG.info(Assigned container ( + allocated + )
{code}
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.
Doug Cutting pointed it out in HADOOP-312:
https://issues.apache.org/jira/browse/HADOOP-312?focusedCommentId=12429498page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12429498
HDFS-1611 also corrected this inconsistency.
This could have been avoided by switching from log4j to slf4j like
CASSANDRA-625 (2010/3) and ZOOKEEPER-850 (2012/1).
--
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
[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
[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:
-
Target Version/s: 2.1.1-beta
Status: Patch Available (was: Open)
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
[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:
-
Status: Open (was: Patch Available)
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
[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:
-
Attachment: HADOOP-9995.patch
Proposed patch against 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 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
[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 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 statement is actually only printed out
in DEBUG-level. Proposed improvements is attached.
was:
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
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 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
[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 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. Proposed improvements is attached.
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 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
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. 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
[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 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. Existing previous issues try to correct this inconsistency. I am
proposing a comprehensive correction over trunk.
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. 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
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. Existing previous issues try to correct this inconsistency. I
am proposing a comprehensive correction over trunk.
--
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
[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 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.
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. Existing previous issues try 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.
--
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
