Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6211918C43 for ; Mon, 11 Jan 2016 23:28:40 +0000 (UTC) Received: (qmail 77338 invoked by uid 500); 11 Jan 2016 23:28:40 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 77160 invoked by uid 500); 11 Jan 2016 23:28:40 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 77131 invoked by uid 99); 11 Jan 2016 23:28:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jan 2016 23:28:39 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id D8F9E2C1F57 for ; Mon, 11 Jan 2016 23:28:39 +0000 (UTC) Date: Mon, 11 Jan 2016 23:28:39 +0000 (UTC) From: "Hudson (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-9639) Inconsistent Logging in BootstrapStandby MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)