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 Fri, 25 Apr 2014 15:52:22 GMT

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

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

[~huangkx], yes, you're correct.  Neither {{hdfsConnect}} nor {{hdfsBuilderConnect}} actually
initiates a network connection.  Instead, they "connect" an {{hdfsFS}} struct to an underlying
Java {{FileSystem}}.  Basically, this stuff is all wrappers over {{FileSystem#get}} in the
Java layer.  There is no actual interaction with the HDFS daemons until you use it with a
function like {{hdfsCreateDirectory}}.  Our use of the word "connect" in the function names
is perhaps slightly misleading.

> 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
>            Assignee: Chris Nauroth
>
> 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