You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2015/04/11 03:28:13 UTC

[jira] [Resolved] (HBASE-5858) When HBase gets executed against Hadoop 2.X "SLF4j:CLASSPATH contains multiple SLF4j binding" warning is displayed

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

Andrew Purtell resolved HBASE-5858.
-----------------------------------
    Resolution: Invalid
      Assignee:     (was: Roman Shaposhnik)

> When HBase gets executed against Hadoop 2.X "SLF4j:CLASSPATH contains multiple SLF4j binding" warning is displayed
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-5858
>                 URL: https://issues.apache.org/jira/browse/HBASE-5858
>             Project: HBase
>          Issue Type: Bug
>          Components: scripts
>    Affects Versions: 0.92.0, 0.92.1
>            Reporter: Roman Shaposhnik
>            Priority: Minor
>         Attachments: error.JPG
>
>
> Since HBase tries to find locations of the Hadoop jars from the environment in certain cases it ends up with extra SLF4j jars coming from Hadoop classpath. When that happens "SLF4j:CLASSPATH contains multiple SLF4j binding" warning gets displayed.
> The good news here is that the warning is just that -- a warning. The bad news is that it seems this issue will be tricky to fix properly. On one hand we would like Hadoop itself to give us transitive closure of the set of jar files required (computing that in the HBase script is a maintenance nightmare). On the other hand that set of jar files could contain some of the very same jars shipped with HBase.
> This problem existed for quiet some time. SLF4j is just the first component to complain.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)