hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6254) hdfsConnect segment fault where namenode not connected
Date Thu, 17 Apr 2014 21:31:16 GMT

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

Chris Nauroth commented on HDFS-6254:
-------------------------------------

I see a hint in the backtrace that this is 2.2.0:

{code}
#9 0x00007f1beb2a39b5 in hdfsExists (fs=0x7f1bb8009640, path=<value optimized out>)
at /home/hkx/hadoop-2.2.0-src/hadoop-hdfs-project/hadoop-hdfs/src/main/native/libhdfs/hdfs.c:1366
{code}

[~huangkx], do you happen to know if this happens with the recently release 2.4.0 or current
trunk too?

This is our C code calling back into the Java layer for {{FileSystem#exists}}, so it's possible
we're doing something wrong there.

> hdfsConnect segment fault where namenode not connected
> ------------------------------------------------------
>
>                 Key: HDFS-6254
>                 URL: https://issues.apache.org/jira/browse/HDFS-6254
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: libhdfs
>    Affects Versions: 2.2.0
>         Environment: Linux Centos 64bit
>            Reporter: huang ken
>
> When namenode is not started, the libhdfs client will cause segment fault while connecting.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message