[
https://issues.apache.org/jira/browse/HDFS-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13975755#comment-13975755
]
Steve Loughran commented on HDFS-6254:
--------------------------------------
thanks for the details. Looking at the latest trace, it's when then native code
calls back into java for a mkdirs(path) operation -it could be that something
being passed down is null or otherwise uninitialized.
That the limit of my JNI knowledge -anyone else got any ideas?
> 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)
