World Library  
Flag as Inappropriate
Email this Article

Moose File System

Article Id: WHEBN0023742362
Reproduction Date:

Title: Moose File System  
Author: World Heritage Encyclopedia
Language: English
Subject: Clustered file system, Ceph (software)
Collection:
Publisher: World Heritage Encyclopedia
Publication
Date:
 

Moose File System

Moose File System
Developer(s) Core Technology[1]
Stable release 2.0.43-1 CE[2][3][4] / November 26, 2014 (2014-11-26)
Operating system Linux, FreeBSD, Solaris, OpenSolaris, Mac OS X
Type Distributed file system
License GNU General Public License v3[5]
Website MooseFS.org

Moose File System (MooseFS) is a distributed file system developed by Core Technology. The lead developer is Jakub Kruszona-Zawadzki. MooseFS aims to be fault-tolerant, high Available, high performance, scalable general-purpose network distributed file system for data centers. Initially proprietary code, it was released to the public as open source on May 5, 2008.

Design

The MooseFS follows similar design principles as Fossil (file system), Google File System, Lustre or Ceph. The file system comprises three components:

  • Metadata server (MDS) — manages the location (layout) of files, file access and namespace hierarchy. The current (1.6.27-5) version of MooseFS does not support multiple metadata servers nor failover. Clients only talk to the MDS to retrieve/update a file's layout and attributes; the data itself is transferred directly between clients and chunk servers. The Metadata server is a user-space daemon; the metadata is kept in memory and lazily stored on local disk.
  • Metalogger server — periodically pulls the metadata from the MDS to store it for backup. Since version 1.6.5, this is an optional feature. Eventually it will be possible to turn the metalogger server into a failover MDS by using the Common Address Redundancy Protocol.
  • Chunk servers (CSS) — store the data and optionally replicate it among themselves. There can be many of them, though the scalability limit has not been published. The biggest cluster reported so far consists of 75 servers.[6] The Chunk server is also a user-space daemon that relies on the underlying local file system to manage the actual storage.
  • Clients — talk to both the MDS and CSS. MooseFS clients mount the file system into user-space via FUSE.

Features

To achieve high reliability and performance MooseFS offers the following features:

  • Fault-tolerance — MooseFS uses replication, data can be replicated across chunkservers, the replication ratio (N) is set per file/directory. If (N-1) replicas fail the data will still be available. At the moment MooseFS does not offer any other technique for fault-tolerance. Fault-tolerance for very big files thus requires vast amount of space - N*filesize instead of filesize+(N*stripesize) as would be the case for RAID 4, RAID 5 or RAID 6.
  • Striping — large files are divided into chunks (up to 64 megabytes) that might be stored on different chunk servers in order to achieve higher aggregate bandwidth.
  • Load balancing — MooseFS attempts to use storage resources equally, the current algorithm seems to take into account only the consumed space.

Hardware, software and networking

Similarly to other cluster-based file systems MooseFS uses commodity hardware running a POSIX compliant operating system. TCP/IP is used as the interconnect.

See also

References

  1. ^ http://www.moosefs.org/contact.html
  2. ^ http://moosefs.com/news/2014-11-26.1.html
  3. ^ http://www.moosefs.org/download.html
  4. ^ http://www.moosefs.org/news-reader/items/moosefs-20-released.html
  5. ^ http://sourceforge.net/p/moosefs/code/ci/master/tree/README
  6. ^ Mariusz Gądarowski (2010-04-01). "MooseFS: Bezpieczny i rozproszony system plików".  

External links

  • Moose File System official website
  • MooseFS project page at SourceForge.net
  • MooseFS GIT repository
This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and USA.gov, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for USA.gov and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
 
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
 
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.
 


Copyright © World Library Foundation. All rights reserved. eBooks from Project Gutenberg are sponsored by the World Library Foundation,
a 501c(4) Member's Support Non-Profit Organization, and is NOT affiliated with any governmental agency or department.