[
https://issues.apache.org/jira/browse/HBASE-11408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14048260#comment-14048260
]
Enis Soztutar commented on HBASE-11408:
---------------------------------------
This is mainly because we blindly append the Hadoop's classpath into our
classpath. Both provide slf4j. I think hbase should still distribute slf4j.
Maybe cleanest solution would be to exclude the slf4j jar from hadoop's
classpath before appending that to our own classpath in both bash and windows
bin scripts. What do you think [~onpduo]?
> "multiple SLF4J bindings" warning messages when running HBase shell
> -------------------------------------------------------------------
>
> Key: HBASE-11408
> URL: https://issues.apache.org/jira/browse/HBASE-11408
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.98.2, 0.98.3
> Reporter: Duo Xu
>
> When running hbase shell, we saw warnings like this:
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/C:/apps/dist/hbase-0.98.0.2.1.3.0-1928-hadoop2/lib/slf4j-log4j12-1.6.4.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/C:/apps/dist/hadoop-2.4.0.2.1.3.0-1928/share/hadoop/common/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
> explanation.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
