[
https://issues.apache.org/jira/browse/HDFS-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13982351#comment-13982351
]
huang ken commented on HDFS-6254:
---------------------------------
Chris Nauroth, thanks again for your explanation.I've retested my test case as
followed：
1. Use hdfsBuilderConnect(connect to a remote host unavailable).
2. Because of hdfsBuilderConnect not initiates a network connection, so
continue to use hdfsCreateDirectory, then it failed with NoRouteToHostException.
3. But if reconnect, SIGSEGV catched.
Is it right ? test.cpp attached.
> 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
> Attachments: test.cpp
>
>
> When namenode is not started, the libhdfs client will cause segment fault
> while connecting.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
