You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Roman Shaposhnik (JIRA)" <ji...@apache.org> on 2012/05/14 18:53:53 UTC

[jira] [Created] (BIGTOP-583) "Class path contains multiple SLF4J bindings" warnings

Roman Shaposhnik created BIGTOP-583:
---------------------------------------

             Summary: "Class path contains multiple SLF4J bindings" warnings
                 Key: BIGTOP-583
                 URL: https://issues.apache.org/jira/browse/BIGTOP-583
             Project: Bigtop
          Issue Type: Bug
          Components: General
    Affects Versions: 0.4.0
            Reporter: Roman Shaposhnik
            Assignee: Roman Shaposhnik
             Fix For: 0.4.0


The following components depend on hadoop-common (package hadoop) and thus get slf4j JARs twice on their classpath (once as a second-level dependency of hadoop-common and second time from their own lib):
  # hadoop-hdfs
  # hadoop-mapreduce
  # hadoop-yarn
  # hbase
  # hive
  # mahout
  # flume

This leads to the harmless, but very annoying "Class path contains multiple SLF4J bindings" warning message to pop up.

Now, this is not a new problem for us -- unfortunately we tend to have multiple instances of the same JARs in the Bigtop's classpath quite a bit. As such one way of "fixing" it would be just making slf4j shut up. The other alternative is to remove slf4j jar files from all the packages mentioned above. This is pretty good, expect for an off chance that *somehow* the component could be used in a standalone mode
where it can't really find hadoop. Not sure how important such a use case would be.

Thoughts?

--
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] (BIGTOP-583) "Class path contains multiple SLF4J bindings" warnings

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

Roman Shaposhnik updated BIGTOP-583:
------------------------------------

    Attachment: BIGTOP-583.patch.txt
    
> "Class path contains multiple SLF4J bindings" warnings
> ------------------------------------------------------
>
>                 Key: BIGTOP-583
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-583
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.4.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.4.0
>
>         Attachments: BIGTOP-583.patch.txt
>
>
> The following components depend on hadoop-common (package hadoop) and thus get slf4j JARs twice on their classpath (once as a second-level dependency of hadoop-common and second time from their own lib):
>   # hadoop-hdfs
>   # hadoop-mapreduce
>   # hadoop-yarn
>   # hbase
>   # hive
>   # mahout
>   # flume
> This leads to the harmless, but very annoying "Class path contains multiple SLF4J bindings" warning message to pop up.
> Now, this is not a new problem for us -- unfortunately we tend to have multiple instances of the same JARs in the Bigtop's classpath quite a bit. As such one way of "fixing" it would be just making slf4j shut up. The other alternative is to remove slf4j jar files from all the packages mentioned above. This is pretty good, expect for an off chance that *somehow* the component could be used in a standalone mode
> where it can't really find hadoop. Not sure how important such a use case would be.
> Thoughts?

--
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] (BIGTOP-583) "Class path contains multiple SLF4J bindings" warnings

Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BIGTOP-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13426760#comment-13426760 ] 

Eli Collins commented on BIGTOP-583:
------------------------------------

There's some relevant discussion on https://issues.cloudera.org/browse/DISTRO-409
                
> "Class path contains multiple SLF4J bindings" warnings
> ------------------------------------------------------
>
>                 Key: BIGTOP-583
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-583
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.4.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.4.0
>
>         Attachments: BIGTOP-583.patch.txt
>
>
> The following components depend on hadoop-common (package hadoop) and thus get slf4j JARs twice on their classpath (once as a second-level dependency of hadoop-common and second time from their own lib):
>   # hadoop-hdfs
>   # hadoop-mapreduce
>   # hadoop-yarn
>   # hbase
>   # hive
>   # mahout
>   # flume
> This leads to the harmless, but very annoying "Class path contains multiple SLF4J bindings" warning message to pop up.
> Now, this is not a new problem for us -- unfortunately we tend to have multiple instances of the same JARs in the Bigtop's classpath quite a bit. As such one way of "fixing" it would be just making slf4j shut up. The other alternative is to remove slf4j jar files from all the packages mentioned above. This is pretty good, expect for an off chance that *somehow* the component could be used in a standalone mode
> where it can't really find hadoop. Not sure how important such a use case would be.
> Thoughts?

--
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] (BIGTOP-583) "Class path contains multiple SLF4J bindings" warnings

Posted by "Bruno Mahé (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BIGTOP-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13282029#comment-13282029 ] 

Bruno Mahé commented on BIGTOP-583:
-----------------------------------

+1
                
> "Class path contains multiple SLF4J bindings" warnings
> ------------------------------------------------------
>
>                 Key: BIGTOP-583
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-583
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.4.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.4.0
>
>         Attachments: BIGTOP-583.patch.txt
>
>
> The following components depend on hadoop-common (package hadoop) and thus get slf4j JARs twice on their classpath (once as a second-level dependency of hadoop-common and second time from their own lib):
>   # hadoop-hdfs
>   # hadoop-mapreduce
>   # hadoop-yarn
>   # hbase
>   # hive
>   # mahout
>   # flume
> This leads to the harmless, but very annoying "Class path contains multiple SLF4J bindings" warning message to pop up.
> Now, this is not a new problem for us -- unfortunately we tend to have multiple instances of the same JARs in the Bigtop's classpath quite a bit. As such one way of "fixing" it would be just making slf4j shut up. The other alternative is to remove slf4j jar files from all the packages mentioned above. This is pretty good, expect for an off chance that *somehow* the component could be used in a standalone mode
> where it can't really find hadoop. Not sure how important such a use case would be.
> Thoughts?

--
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] (BIGTOP-583) "Class path contains multiple SLF4J bindings" warnings

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

Roman Shaposhnik updated BIGTOP-583:
------------------------------------

    Attachment: BIGTOP-583.patch.txt
    
> "Class path contains multiple SLF4J bindings" warnings
> ------------------------------------------------------
>
>                 Key: BIGTOP-583
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-583
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.4.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.4.0
>
>         Attachments: BIGTOP-583.patch.txt
>
>
> The following components depend on hadoop-common (package hadoop) and thus get slf4j JARs twice on their classpath (once as a second-level dependency of hadoop-common and second time from their own lib):
>   # hadoop-hdfs
>   # hadoop-mapreduce
>   # hadoop-yarn
>   # hbase
>   # hive
>   # mahout
>   # flume
> This leads to the harmless, but very annoying "Class path contains multiple SLF4J bindings" warning message to pop up.
> Now, this is not a new problem for us -- unfortunately we tend to have multiple instances of the same JARs in the Bigtop's classpath quite a bit. As such one way of "fixing" it would be just making slf4j shut up. The other alternative is to remove slf4j jar files from all the packages mentioned above. This is pretty good, expect for an off chance that *somehow* the component could be used in a standalone mode
> where it can't really find hadoop. Not sure how important such a use case would be.
> Thoughts?

--
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] (BIGTOP-583) "Class path contains multiple SLF4J bindings" warnings

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

Roman Shaposhnik updated BIGTOP-583:
------------------------------------

    Attachment:     (was: BIGTOP-583.patch.txt)
    
> "Class path contains multiple SLF4J bindings" warnings
> ------------------------------------------------------
>
>                 Key: BIGTOP-583
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-583
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.4.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.4.0
>
>         Attachments: BIGTOP-583.patch.txt
>
>
> The following components depend on hadoop-common (package hadoop) and thus get slf4j JARs twice on their classpath (once as a second-level dependency of hadoop-common and second time from their own lib):
>   # hadoop-hdfs
>   # hadoop-mapreduce
>   # hadoop-yarn
>   # hbase
>   # hive
>   # mahout
>   # flume
> This leads to the harmless, but very annoying "Class path contains multiple SLF4J bindings" warning message to pop up.
> Now, this is not a new problem for us -- unfortunately we tend to have multiple instances of the same JARs in the Bigtop's classpath quite a bit. As such one way of "fixing" it would be just making slf4j shut up. The other alternative is to remove slf4j jar files from all the packages mentioned above. This is pretty good, expect for an off chance that *somehow* the component could be used in a standalone mode
> where it can't really find hadoop. Not sure how important such a use case would be.
> Thoughts?

--
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