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

Posted to hdfs-issues@hadoop.apache.org by "Chris Nauroth (JIRA)" <ji...@apache.org> on 2014/11/22 02:02:57 UTC

[jira] [Resolved] (HDFS-7425) NameNode block deletion logging uses incorrect appender.

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

Chris Nauroth resolved HDFS-7425.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 2.6.1
     Hadoop Flags: Reviewed

I committed this to branch-2 and branch-2.6.  Haohui, thank you for the code review.

> 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
>            Priority: Minor
>             Fix For: 2.6.1
>
>         Attachments: HDFS-7425-branch-2.1.patch
>
>
> 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)