[ 
https://issues.apache.org/jira/browse/HDFS-9639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15092936#comment-15092936
 ] 

Hudson commented on HDFS-9639:
------------------------------

FAILURE: Integrated in Hadoop-trunk-Commit #9086 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/9086/])
HDFS-9639. Inconsistent Logging in BootstrapStandby. (Contributed by (arp: rev 
de37f37543c2fb07ca53bb6000d50b36ec70d084)
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/ha/BootstrapStandby.java


> Inconsistent Logging in BootstrapStandby
> ----------------------------------------
>
>                 Key: HDFS-9639
>                 URL: https://issues.apache.org/jira/browse/HDFS-9639
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: ha
>    Affects Versions: 2.7.1
>            Reporter: BELUGA BEHR
>            Assignee: Xiaobing Zhou
>            Priority: Minor
>             Fix For: 2.8.0
>
>         Attachments: HADOOP-12674.001.patch
>
>
> {code}
> /* Line 379 */
>       if (LOG.isDebugEnabled()) {
>         LOG.debug(msg, e);
>       } else {
>         LOG.fatal(msg);
>       }
> {code}
> Why would message, considered "fatal" under most operating circumstances be 
> considered "debug" when debugging is on.  This is confusing to say the least. 
>  If there is a problem and the user attempts to debug the situation, they may 
> be filtering on "fatal" messages and miss the exception.
> Please consider using only the fatal logging, and including the exception.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to