hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3808) fuse_dfs: postpone libhdfs intialization until after fork
Date Fri, 17 Aug 2012 00:37:38 GMT

    [ https://issues.apache.org/jira/browse/HDFS-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436479#comment-13436479

Hudson commented on HDFS-3808:

Integrated in Hadoop-Mapreduce-trunk-Commit #2621 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2621/])
    HDFS-3808. fuse_dfs: postpone libhdfs intialization until after fork. Contributed by Colin
Patrick McCabe. (Revision 1374106)

     Result = FAILURE
atm : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1374106
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/native/fuse-dfs/fuse_dfs.c
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/native/fuse-dfs/fuse_init.c

> 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
>             Fix For: 2.2.0-alpha
>         Attachments: HDFS-3808.001.patch, HDFS-3808.002.patch, HDFS-3808.003.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


View raw message