Comparison of distributed file systems
In computing, a distributed file system (DFS) or network file system is any file system that allows access to files from multiple hosts sharing via a computer network. This makes it possible for multiple users on multiple machines to share files and storage resources.
Distributed file systems differ in their performance, mutability of content, handling of concurrent writes, handling of permanent or temporary loss of nodes or storage, and their policy of storing content.
Locally managed
FOSS
Client | Written in | License | Access API | High availability | Shards | Efficient Redundancy | Redundancy Granularity | Initial release year | Memory requirements (GB) |
---|---|---|---|---|---|---|---|---|---|
Alluxio (Virtual Distributed File System) | Java | Apache License 2.0 | HDFS, FUSE, HTTP/REST, S3 | hot standby | No | Replication[1] | File[2] | 2013 | |
Ceph | C++ | LGPL | librados (C, C++, Python, Ruby), S3, Swift, FUSE | Yes | Yes | Pluggable erasure codes[3] | Pool[4] | 2010 | 1 per TB of storage |
Coda | C | GPL | C | Yes | Yes | Replication | Volume[5] | 1987 | |
GlusterFS | C | GPLv3 | libglusterfs, FUSE, NFS, SMB, Swift, libgfapi | mirror | Yes | Reed-Solomon[6] | Volume[7] | 2005 | |
HDFS | Java | Apache License 2.0 | Java and C client, HTTP, FUSE[8] | transparent master failover | No | Reed-Solomon[9] | File[10] | 2005 | |
IPFS | Go | Apache 2.0 or MIT | HTTP gateway, FUSE, Go client, Javascript client, command line tool | Yes | with IPFS Cluster | Replication[11] | Block[12] | 2015[13] | |
JuiceFS | Go | Apache License 2.0 | POSIX, FUSE, HDFS, S3 | Yes | Yes | Reed-Solomon | Object | 2021 | |
Kertish-DFS | Go | GPLv3 | HTTP(REST), CLI, C# Client, Go Client | Yes | Replication | 2020 | |||
LizardFS | C++ | GPLv3 | POSIX, FUSE, NFS-Ganesha, Ceph FSAL (via libcephfs) | master | No | Reed-Solomon[14] | File[15] | 2013 | |
Lustre | C | GPLv2 | POSIX, NFS-Ganesha, NFS, SMB | Yes | Yes | No redundancy[16][17] | No redundancy[18][19] | 2003 | |
MinIO | Go | AGPL3.0 | AWS S3 API, FTP, SFTP | Yes | Yes | Reed-Solomon[20] | Object[21] | 2014 | |
MooseFS | C | GPLv2 | POSIX, FUSE | master | No | Replication[22] | File[23] | 2008 | |
OpenAFS | C | IBM Public License | Virtual file system, Installable File System | Replication | Volume[24] | 2000 [25] | |||
OpenIO[26] | C | AGPLv3 / LGPLv3 | Native (Python, C, Java), HTTP/REST, S3, Swift, FUSE (POSIX, NFS, SMB, FTP) | Yes | Pluggable erasure codes[27] | Object[28] | 2015 | 0.5 | |
Ori[29] | C, C++ | MIT | libori, FUSE | Replication | Filesystem[30] | 2012 | |||
Quantcast File System | C | Apache License 2.0 | C++ client, FUSE (C++ server: MetaServer and ChunkServer are both in C++) | master | No | Reed-Solomon[31] | File[32] | 2012 | |
RozoFS | C, Python | GPLv2 | FUSE, SMB, NFS, key/value | Yes | Mojette[33] | Volume[34] | 2011[35] | ||
SeaweedFS | Go, Java | Apache License 2.0 | HTTP (REST), POSIX, FUSE, S3, HDFS | requires CockroachDB, undocumented config | Reed-Solomon[36] | Volume[37] | 2015 | ||
Storj | Go | Apache License 2.0, Affero General Public License v3 | HTTP (REST), S3, Native (Go, C, Python, Java) | Yes | Reed-Solomon[38] | Object[38] | 2018 | ||
Tahoe-LAFS | Python | GNU GPL[39] | HTTP (browser or CLI), SFTP, FTP, FUSE via SSHFS, pyfilesystem | Reed-Solomon[40] | File[41] | 2007 | |||
XtreemFS | Java, C++ | BSD License | libxtreemfs (Java, C++), FUSE | Replication[42] | File[43] | 2009 |
Proprietary
Client | Written in | License | Access API |
---|---|---|---|
BeeGFS | C / C++ | FRAUNHOFER FS (FhGFS) EULA,[44]
GPLv2 client |
POSIX |
ObjectiveFS[45] | C | Proprietary | POSIX, FUSE |
Spectrum Scale (GPFS) | C, C++ | Proprietary | POSIX, NFS, SMB, Swift, S3, HDFS |
MapR-FS | C, C++ | Proprietary | POSIX, NFS, FUSE, S3, HDFS, CLI |
PanFS | C, C++ | Proprietary | DirectFlow, POSIX, NFS, SMB/CIFS, HTTP, CLI |
Infinit[46] | C++ | Proprietary (to be open sourced)[47] | FUSE, Installable File System, NFS/SMB, POSIX, CLI, SDK (libinfinit) |
Isilon OneFS | C/C++ | Proprietary | POSIX, NFS, SMB/CIFS, HDFS, HTTP, FTP, SWIFT Object, CLI, Rest API |
Qumulo | C/C++ | Proprietary | POSIX, NFS, SMB/CIFS, CLI, Rest API |
Scality | C | Proprietary | FUSE, NFS, REST, AWS S3 |
Quobyte | Java, C++ | Proprietary | POSIX, FUSE, NFS, SMB/CIFS, HDFS, AWS S3, TensorFlow Plugin, CLI, Rest API |
Remote access
Name | Run by | Access API |
---|---|---|
Amazon S3 | Amazon.com | HTTP (REST/SOAP) |
Google Cloud Storage | HTTP (REST) | |
SWIFT (part of OpenStack) | Rackspace, Hewlett-Packard, others | HTTP (REST) |
Microsoft Azure | Microsoft | HTTP (REST) |
IBM Cloud Object Storage | IBM (formerly Cleversafe)[48] | HTTP (REST) |
Comparison
Some researchers have made a functional and experimental analysis of several distributed file systems including HDFS, Ceph, Gluster, Lustre and old (1.6.x) version of MooseFS, although this document is from 2013 and a lot of information are outdated (e.g. MooseFS had no HA for Metadata Server at that time).[49]
The cloud based remote distributed storage from major vendors have different APIs and different consistency models.[50]
References
- "Caching: Managing Data Replication in Alluxio".
- "Caching: Managing Data Replication in Alluxio".
- "Erasure Code Profiles".
- "Pools".
- Satyanarayanan, Mahadev; Kistler, James J.; Kumar, Puneet; Okasaki, Maria E.; Siegel, Ellen H.; Steere, David C. "Coda: A Highly Available File System for a Distributed Workstation Environment" (PDF).
{{cite journal}}
: Cite journal requires|journal=
(help) - "Erasure coding implementation". GitHub. 2 November 2021.
- "Setting up GlusterFS Volumes".
- "MountableHDFS".
- "HDFS-7285 Erasure Coding Support inside HDFS".
- "Apache Hadoop: setrep".
- Erasure coding plan: "Reed-Solomon layer over IPFS #196". GitHub., "Erasure Coding Layer #6". GitHub.
- "CLI Commands: ipfs bitswap wantlist".
- "Why The Internet Needs IPFS Before It's Too Late". 4 October 2015.
- "Configuring Replication Modes".
- "Configuring Replication Modes: Set and show the goal of a file/directory".
- "Lustre Operations Manual: What a Lustre File System Is (and What It Isn't)".
- Reed-Solomon in progress: "LU-10911 FLR2: Erasure coding".
- "Lustre Operations Manual: Lustre Features".
- File-level redundancy plan: "File Level Redundancy Solution Architecture".
- "MinIO Erasure Code Quickstart Guide".
- "MinIO Storage Class Quickstart Guide". GitHub.
- Only available in the proprietary version 4.x "[feature] erasure-coding #8". GitHub.
- "mfsgoal(1)".
- "Replicating Volumes (Creating Read-only Volumes)".
- "OpenAFS".
- "OpenIO SDS Documentation". docs.openio.io.
- "Erasure Coding".
- "Declare Storage Policies".
- "Ori: A Secure Distributed File System".
- Mashtizadeh, Ali Jose; Bittau, Andrea; Huang, Yifeng Frank; Mazières, David. "Replication, History, and Grafting in the Ori File System" (PDF).
{{cite journal}}
: Cite journal requires|journal=
(help) - "The Quantcast File System" (PDF).
- "qfs/src/cc/tools/cptoqfs_main.cc". GitHub. 8 December 2021.
- "About RozoFS: Mojette Transform".
- "Setting up RozoFS: Exportd Configuration File".
- "Initial commit". GitHub.
- "Erasure Coding for warm storage". GitHub.
- "Replication". GitHub.
- "Storj: A Decentralized Cloud Storage Network Framework v3.0" (PDF). 30 October 2018.
- "About Tahoe-LAFS". GitHub. 24 February 2022.
- "zfec -- a fast C implementation of Reed-Solomon erasure coding". GitHub. 24 February 2022.
- "Tahoe-LAFS Architecture: File Encoding".
- "Under the Hood: File Replication".
- "Quickstart: Replicate A File".
- "FRAUNHOFER FS (FhGFS) END USER LICENSE AGREEMENT". Fraunhofer Society. 2012-02-22.
- "ObjectiveFS official website".
- "The Infinit Storage Platform".
- "Infinit's Open Source Projects". 13 August 2019.
- "IBM Plans to Acquire Cleversafe for Object Storage in Cloud". www-03.ibm.com. 2015-10-05. Retrieved 2019-05-06.
- Séguin, Cyril; Depardon, Benjamin; Le Mahec, Gaël. "Analysis of Six Distributed File Systems" (PDF). HAL.
- "Data Consistency Models of Public Cloud Storage Services: Amazon S3, Google Cloud Storage and Windows Azure Storage". SysTutorials. 4 February 2014. Retrieved 19 June 2017.