[
https://issues.apache.org/jira/browse/HDFS-7712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14304365#comment-14304365
]
Arpit Agarwal commented on HDFS-7712:
-------------------------------------
Hi [~andrew.wang], after this change I get the following error when invoking
_hdfs namenode -format_
{code}
15/02/03 15:50:25 ERROR namenode.NameNode: Failed to start namenode.
java.lang.ClassCastException: org.apache.log4j.Logger cannot be cast to
org.apache.commons.logging.Log
at
org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1557)
15/02/03 15:50:25 INFO util.ExitUtil: Exiting with status 1
{code}
Just curious if this looks familiar to you. Do I need additional configuration?
Thanks.
> Switch blockStateChangeLog to use slf4j
> ---------------------------------------
>
> Key: HDFS-7712
> URL: https://issues.apache.org/jira/browse/HDFS-7712
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Affects Versions: 2.7.0
> Reporter: Andrew Wang
> Assignee: Andrew Wang
> Priority: Minor
> Attachments: hdfs-7712.001.patch, hdfs-7712.002.patch,
> hdfs-7712.003.patch, hdfs-7712.004.patch
>
>
> As pointed out in HDFS-7706, updating blockStateChangeLog to use slf4j will
> save a lot of string construction costs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
