[
https://issues.apache.org/jira/browse/HDFS-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436158#comment-13436158
]
Andy Isaacson commented on HDFS-3808:
-------------------------------------
It's not accurate to say "we should not call fork", because forking to exec a
child process should work just fine. The problem here is the daemonize()
pattern, where we fork and continue execution in the child process in order to
fiddle parent/child relationships and pgrp mappings.
I'll update the description accordingly.
Reviewing the patch now.
> fuse_dfs: postpone libhdfs intialization until after fork
> ---------------------------------------------------------
>
> Key: HDFS-3808
> URL: https://issues.apache.org/jira/browse/HDFS-3808
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: fuse-dfs
> Affects Versions: 2.2.0-alpha
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Priority: Critical
> Attachments: HDFS-3808.001.patch
>
>
> {{libhdfs}} may create threads or initialize internal JNI data structures
> when it is used. So we should not call fork() after the library is first
> used.
> Unfortunately, fuse_dfs is doing just this-- initializing libhdfs in its
> {{main}} function, prior to calling {{fuse_main}} which does a {{daemonize}}
> (which involves forking.) We should correct this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
