From: Robert S. <rsa...@ne...> - 2012-02-14 00:11:55
|
I have to disagree. mfsmaster is very sensitive to load. You really want to run a dedicated master server. Setting up a (virtual) machine or even multiple (virtual) machines to mount the file system is a better idea. Ensure that you disable all asynchronous file access in Samba. FUSE and sendfile() is not a great combination. I would also recommend having a mount per SMB share. For example if you plan to have 3 shares called "tools", "docs" and "tmp" then I would mount MooseFS on three folders: /mnt/mfs_tools, /mnt/mfs_docs and /mnt/mfs_tmp and share those points using SMB. This implies running 3 instances of mfsmount. It works around some bottlenecks in mfsmount. Robert On 2/13/12 1:38 PM, JJ wrote: > Perfect! > > Thank you. > > > JJ > Support Engineer > Cirrhus9.com > > On 02/13/2012 01:38 PM, Travis Hein wrote: >> ... >> But functionally there is no technical consideration why you could not >> run mfsmount on the mfsmaster node. >> ... > ------------------------------------------------------------------------------ > Try before you buy = See our experts in action! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-dev2 > _______________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users |