You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Roman Shaposhnik (JIRA)" <ji...@apache.org> on 2012/04/23 17:37:35 UTC

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

Roman Shaposhnik created HBASE-5858:
---------------------------------------

             Summary: 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.1, 0.92.0
            Reporter: Roman Shaposhnik
            Assignee: Roman Shaposhnik
            Priority: Minor


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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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

Posted by "Praveen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-5858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260182#comment-13260182 ] 

Praveen commented on HBASE-5858:
--------------------------------

Hi 
I am also facing the same problem When i try to create table in HBase i am getting this error. What should i do ?

can anyone tell me way to fix it.

Any help is appreciated
                
> 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
>            Assignee: 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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

Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-5858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260111#comment-13260111 ] 

Andrew Purtell commented on HBASE-5858:
---------------------------------------

Does it make sense to factor common dependencies and symlink with Puppet in say the BigTop distro framework Roman?

Since we support multiple versions of Hadoop it's unlikely we can avoid multiple versions of jars in the class path from tarball distributions. 
                
> 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
>            Assignee: Roman Shaposhnik
>            Priority: Minor
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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

Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-5858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260185#comment-13260185 ] 

Roman Shaposhnik commented on HBASE-5858:
-----------------------------------------

Praveen, if what you're getting is an *error* you must be having a different problem. I get the very same messages but they are harmless warnings.
                
> 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
>            Assignee: 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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

Posted by "Praveen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-5858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Praveen updated HBASE-5858:
---------------------------

    Attachment: error.JPG
    
> 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
>            Assignee: 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira