hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7425) NameNode block deletion logging uses incorrect appender.
Date Sat, 22 Nov 2014 00:41:34 GMT

    [ https://issues.apache.org/jira/browse/HDFS-7425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14221651#comment-14221651
] 

Hudson commented on HDFS-7425:
------------------------------

FAILURE: Integrated in Hadoop-trunk-Commit #6590 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/6590/])
HDFS-7425. NameNode block deletion logging uses incorrect appender. Contributed by Chris Nauroth.
(cnauroth: rev b8c094b0754099f13d668081b4afcf0644e325c3)
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt


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

Mime
View raw message