hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8884) DEBUG should be WARN for DEBUG util.NativeCodeLoader: Failed to load native-hadoop with error: java.lang.UnsatisfiedLinkError
Date Mon, 08 Oct 2012 21:40:03 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-8884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471889#comment-13471889
] 

Todd Lipcon commented on HADOOP-8884:
-------------------------------------

Yea, I think it would be worth distinguishing between the reasons. For example, if they fail
to load due to a platform mismatch (eg 64-bit libs on 32-bit JDK) or due to a dependency mismatch
(eg built against a different glibc than available on the system), it's worth WARNing. But
non-presence should not WARN.
                
> DEBUG should be WARN for DEBUG util.NativeCodeLoader: Failed to load native-hadoop with
error: java.lang.UnsatisfiedLinkError
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-8884
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8884
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: util
>    Affects Versions: 2.0.1-alpha
>            Reporter: Anthony Rojas
>            Assignee: Anthony Rojas
>             Fix For: 2.0.3-alpha
>
>         Attachments: HADOOP-8884.patch, HADOOP-8884.patch, HADOOP-8884-v2.patch
>
>
> Recommending to change the following debug message and promote it to a warning instead:
> 12/07/02 18:41:44 DEBUG util.NativeCodeLoader: Failed to load native-hadoop with error:
java.lang.UnsatisfiedLinkError: /usr/lib/hadoop/lib/native/libhadoop.so.1.0.0: /lib64/libc.so.6:
version `GLIBC_2.6' not found (required by /usr/lib/hadoop/lib/native/libhadoop.so.1.0.0)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message