Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Mon, 11 Jan 2016 18:23:39 +0000 (UTC)
From: "Xiaobing Zhou (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12924022.1450884059000.75593.1452536619932@Atlassian.JIRA>
In-Reply-To: <JIRA.12924022.1450884059000@Atlassian.JIRA>
References: <JIRA.12924022.1450884059000@Atlassian.JIRA>
 <JIRA.12924022.1450884059744@arcas>
Subject: [jira] [Updated] (HADOOP-12674) BootstrapStandby - Inconsistent
 Logging
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Xiaobing Zhou updated HADOOP-12674:
-----------------------------------
    Status: Patch Available  (was: Open)

> BootstrapStandby - Inconsistent Logging
> ---------------------------------------
>
>                 Key: HADOOP-12674
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12674
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ha
>    Affects Versions: 2.7.1
>            Reporter: BELUGA BEHR
>            Assignee: Xiaobing Zhou
>            Priority: Minor
>         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)