hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig Macdonald (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (HADOOP-4) tool to mount dfs on linux
Date Wed, 20 Feb 2008 15:53:48 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570683#action_12570683
] 

craigm edited comment on HADOOP-4 at 2/20/08 7:52 AM:
---------------------------------------------------------------

For #1, I think thats an fstab line, not an autofs line, perhaps? I'm not sure the fuse version
will make any difference, mount will only pass through the source path, the dest path and
the -o options. Would it be possible to keep all options for fuse_dfs.c in -o options? On
the other hand, if a shell script is always needed to set the CLASSPATH and LD_LIBRARY_PATH
options, then it is not as important how the options are set from fstab or autofs. (LD_LIBRARY_PATH
could be fixed bya  /etc/ld.conf.d entry)

My test had no load on the namenode, and usage of the namenode CPU looks low. In contrast,
the fuse_dcs CPU usage was high.

I would like to profile or jconsole the fuse_dfs binary, but the getJNIEnv() method in src/c++/libhdfs/hdfsJniHelper.c
could be a bit more helpful for passing agument to the JVM initialisation. Essentially, it
only allows fills in -Djava.class.path from the CLASSPATH to be set, not any other arbitrary
system properties or -X options etc, bah.  Reported separately as HADOOP-2857.

Will attach bash script shortly.

C

      was (Author: craigm):
    For #1, I think thats an fstab line, not an autofs line, perhaps? I'm not sure the fuse
version will make any difference, mount will only pass through the source path, the dest path
and the -o options. Would it be possible to keep all options for fuse_dfs.c in -o options?
On the other hand, if a shell script is always needed to set the CLASSPATH and LD_LIBRARY_PATH
options, then it is not as important how the options are set from fstab or autofs. (LD_LIBRARY_PATH
could be fixed bya  /etc/ld.conf.d entry)

My test had no load on the namenode, and usage of the namenode CPU looks low. In contrast,
the fuse_dcs CPU usage was high.

I would like to profile or jconsole the fuse_dfs binary, but the getJNIEnv() method in src/c++/libhdfs/hdfsJniHelper.c
could be a bit more helpful for passing agument to the JVM initialisation. Essentially, it
only allows fills in -Djava.class.path from the CLASSPATH to be set, not any other arbitrary
system properties or -X options etc, bah. 

Will attach bash script shortly.

C
  
> tool to mount dfs on linux
> --------------------------
>
>                 Key: HADOOP-4
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: fs
>    Affects Versions: 0.5.0
>         Environment: linux only
>            Reporter: John Xing
>            Assignee: Doug Cutting
>         Attachments: fuse-dfs.tar.gz, fuse-dfs.tar.gz, fuse-dfs.tar.gz, fuse-hadoop-0.1.0_fuse-j.2.2.3_hadoop.0.5.0.tar.gz,
fuse-hadoop-0.1.0_fuse-j.2.4_hadoop.0.5.0.tar.gz, fuse-hadoop-0.1.1.tar.gz, fuse-j-hadoopfs-03.tar.gz,
fuse_dfs.c, fuse_dfs.c, fuse_dfs.sh, Makefile
>
>
> tool to mount dfs on linux

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message