hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-7425) NameNode block deletion logging uses incorrect appender.
Date Thu, 16 Jul 2015 01:04:05 GMT

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

Vinod Kumar Vavilapalli updated HDFS-7425:
------------------------------------------
    Labels: 2.6.1-candidate  (was: )

> 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
>              Labels: 2.6.1-candidate
>             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)

Mime
View raw message