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

Pete Wyckoff commented on HADOOP-4:
-----------------------------------

Hi Craig,

I may be using an older fuse? I have #dfs#dfs://hadoopNN01.facebook.com:9000 
/mnt/hdfs    fuse    allow_other,rw    0 0 

For performance, it's really fast when there's 0 load on the namenode, but 
start running a couple of jobs and it gets killed.  Obviously because one 
operation may require multiple fuse calls and thus multiple dfs calls versus 
the single one for bin/hadoop dfs.   I'm noticing that all the critical 
sections in the namenode do things like logging to the debug log *IN* the 
critical section. And since everything locks fsRoot, just one job can really 
hose a real-time system. I don't see anything to do here other than trying to 
fix these after verifying with jconsole this is the problem.

And I will add the autofs destroy function this week.

So, what do you think I should do for #1, revert to the older configuration 
code? (which was way nicer anyway). Do you have your bash script so I can use 
it too?

thanks, pete



> 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, 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.

Reply via email to