[
https://issues.apache.org/jira/browse/HDFS-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13976037#comment-13976037
]
Chris Nauroth commented on HDFS-6254:
-------------------------------------
The line numbers in the latest backtrace match up with the current trunk code.
Thank you for retesting.
{{hdfsConnect}} is supposed to return {{NULL}} if the connection fails. This
is covered by tests in a few places, such as test_libhdfs_read.c:
{code}
hdfsFS fs = hdfsConnect("default", 0);
if (!fs) {
fprintf(stderr, "Oops! Failed to connect to hdfs!\n");
exit(-1);
}
{code}
[~huangkx], are you not seeing a {{NULL}} return in your environment? Can you
post a minimal code snippet that repros the problem for you?
> 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)
