Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Fri, 21 Nov 2014 18:55:35 +0000 (UTC)
From: "Chris Nauroth (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12757052.1416596124000.555444.1416596135779@Atlassian.JIRA>
In-Reply-To: <JIRA.12757052.1416596124000@Atlassian.JIRA>
References: <JIRA.12757052.1416596124000@Atlassian.JIRA>
 <JIRA.12757052.1416596124225@arcas>
Subject: [jira] [Created] (HDFS-7425) NameNode block deletion logging uses
 incorrect appender.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Chris Nauroth created HDFS-7425:
-----------------------------------

             Summary: NameNode block deletion logging uses incorrect appender.
                 Key: HDFS-7425
                 URL: https://issues.apache.org/jira/browse/HDFS-7425
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: namenode
    Affects Versions: 2.6.0
            Reporter: Chris Nauroth
            Assignee: Chris Nauroth


The NameNode uses 2 separate Log4J appenders for tracking state changes.  The appenders are named "org.apache.hadoop.hdfs.StateChange" and "BlockStateChange".  The intention of BlockStateChange is to separate more verbose block state change logging and allow it to be configured separately.  In branch-2, there is some block state change logging that incorrectly goes to the "org.apache.hadoop.hdfs.StateChange" appender though.  The bug is not present in trunk.


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