[
https://issues.apache.org/jira/browse/HDFS-9524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058251#comment-15058251
]
Bob Hansen commented on HDFS-9524:
----------------------------------
New patch to address your comments.
bq. As far as I can tell you'd have the same problem if you deleted the
FileSystem in the FileSystem::Connect callback on a failed connect. Maybe it's
worth having a rule/comment about deleting the filesystem from within the
context of a callback?
That's a good suggestion. I added comments to the public interface. I also
spent some time thinking about how I would want to respond at run-time to
detecting the error, and the current default behavior of dump core for easy
debugging and terminate the app is probably the best one. I added some output
to stderr to make it even more explicit what the error case is.
> libhdfs++ deadlocks in Filesystem::New if NN conneciton fails
> -------------------------------------------------------------
>
> Key: HDFS-9524
> URL: https://issues.apache.org/jira/browse/HDFS-9524
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: hdfs-client
> Reporter: Bob Hansen
> Assignee: Bob Hansen
> Attachments: HDFS-9524.HDFS-8707.000.patch,
> HDFS-9524.HDFS-8707.001.patch, HDFS-9524.HDFS-8707.002.patch
>
>
> FileSystem::New attempts to free the new FileSystem if the connection fails.
> Unfortunately, it's in the middle of a callback from the filesystem's
> threadpool, and attempts to join the worker thread while running the worker
> thread.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
