hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "huang ken (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6254) hdfsConnect segment fault where namenode not connected
Date Mon, 21 Apr 2014 07:37:15 GMT

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

huang ken commented on HDFS-6254:
---------------------------------

Steve Loughran, #1. Updated jdk version to 7u55, also segment fault.
Chris Nauroth ,   #2. Updated hadoop version to 2.4.0, also segment fault.

No matter which version of hadoop i use, hdfsConnect() never return error or NULL, until i
call hdfsCreateDirectory() or hdfsExists(), is it right ?

> 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