hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-8005) Multiple SLF4J binding message in .out file for all daemons
Date Tue, 13 Mar 2012 14:45:34 GMT

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

Jason Lowe updated HADOOP-8005:
-------------------------------

    Attachment: slf4j-assembly-removal.patch

We can also address the problem by removing the slf4j jars from the hdfs and mapreduce assemblies.
 HDFS no longer seems to need slf4j, and we can explicitly filter the slf4j jars from the
mapreduce project.  Patch attached for comment.

If desired, I can file the HDFS and MAPREDUCE JIRAs to get the corresponding changes into
those projects.
                
> Multiple SLF4J binding message in .out file for all daemons
> -----------------------------------------------------------
>
>                 Key: HADOOP-8005
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8005
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: scripts
>    Affects Versions: 0.23.0
>            Reporter: Joe Crobak
>         Attachments: slf4j-assembly-removal.patch
>
>
> When I start the NameNode or DataNode using sbin/hadoop-daemon.sh, I get a variant of
the following error on stdout:
> {noformat}
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in [jar:file:/Users/joecrow/Code/hadoop-0.23.0/share/hadoop/common/lib/slf4j-log4j12-1.5.11.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in [jar:file:/Users/joecrow/Code/hadoop-0.23.0/share/hadoop/hdfs/lib/slf4j-log4j12-1.5.11.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
> {noformat}

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

        

Mime
View raw message