[ https://issues.apache.org/jira/browse/HDFS-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13976126#comment-13976126 ]
Chris Nauroth commented on HDFS-6254: ------------------------------------- To clarify my earlier comment, the test is probably not actually covering the case of a connection failure, because it waits for the cluster to be running in the background before starting. It would still be interesting to see the code sample that you're using though. > 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)