You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2021/03/20 01:40:00 UTC
[jira] [Commented] (HBASE-19587) [sfl4j] " Class path contains
multiple SLF4J binding" complaint
[ https://issues.apache.org/jira/browse/HBASE-19587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17305264#comment-17305264 ]
Duo Zhang commented on HBASE-19587:
-----------------------------------
Do we still have this message when starting HBase?
> [sfl4j] " Class path contains multiple SLF4J binding" complaint
> ---------------------------------------------------------------
>
> Key: HBASE-19587
> URL: https://issues.apache.org/jira/browse/HBASE-19587
> Project: HBase
> Issue Type: Sub-task
> Affects Versions: 2.0.0
> Reporter: Michael Stack
> Priority: Major
>
> I get the below staring a cluster in distribute mode.
> $ ./hbase/bin/start-hbase.sh --config ~/conf_hbase
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in [jar:file:/home/stack/hbase-2.0.0-beta-1-SNAPSHOT/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in [jar:file:/home/stack/hadoop-2.8.2/share/hadoop/common/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
> SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in [jar:file:/home/stack/hbase-2.0.0-beta-1-SNAPSHOT/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in [jar:file:/home/stack/hadoop-2.8.2/share/hadoop/common/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
> SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
> I can make it go away if I do the following in hbase-env.sh:
> export HBASE_DISABLE_HADOOP_CLASSPATH_LOOKUP=true
> ...which disables including hadoop jars on our classpath, a facility that came in years ago w/ this commit.
> tree b7e93ae4c62f22e5d4ce221cafaaee293c7b67ce
> parent d1619bceb3142f3ab8c134365e18a150fbd5b9bf
> author Enis Soztutar <en...@apache.org> Fri Feb 27 16:27:40 2015 -0800
> committer Enis Soztutar <en...@apache.org> Fri Feb 27 16:27:40 2015 -0800
> HBASE-13120 Allow disabling hadoop classpath and native library lookup (Siddharth Wagle)
> Adding hadoop to our CLASSPATH seems to be around for years:
> tree eb5ee09ac9894d264f1a2d1653f5f5eb6684f2fb
> parent d2fb2d5e2494834947799c5f4fbd72955e7fdba1
> author Michael Stack <st...@apache.org> Sat Mar 3 16:47:55 2012 +0000
> committer Michael Stack <st...@apache.org> Sat Mar 3 16:47:55 2012 +0000
> HBASE-5286 bin/hbase's logic of adding Hadoop jar files to the classpath is fragile when presented with split packaged Hadoop 0.23 installation
--
This message was sent by Atlassian Jira
(v8.3.4#803005)