[
https://issues.apache.org/jira/browse/HDFS-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Isaacson updated HDFS-3808:
--------------------------------
Description:
{{libhdfs}} may create threads or initialize internal JNI data structures when
it is used. So we should be careful to {{daemonize()}} before initializing
{{libhdfs}}, not after.
Unfortunately, fuse_dfs is doing just this -- initializing libhdfs in its
{{main}} function, prior to calling {{fuse_main}} which does a {{daemonize}}.
{{daemonize()}} does not preserve threads, because it is implemented by
{{fork()}}ing and then continuing execution in the child and allowing the
parent to {{exit()}}.
was:
{{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.
> 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 be careful to {{daemonize()}} before
> initializing {{libhdfs}}, not after.
> Unfortunately, fuse_dfs is doing just this -- initializing libhdfs in its
> {{main}} function, prior to calling {{fuse_main}} which does a {{daemonize}}.
> {{daemonize()}} does not preserve threads, because it is implemented by
> {{fork()}}ing and then continuing execution in the child and allowing the
> parent to {{exit()}}.
--
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
