You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "BELUGA BEHR (JIRA)" <ji...@apache.org> on 2015/12/23 16:21:46 UTC

[jira] [Created] (HADOOP-12674) BootstrapStandby - Inconsistent Logging

BELUGA BEHR created HADOOP-12674:
------------------------------------

             Summary: 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
            Priority: Minor


{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)