gitlab-com-seaweedfs/seaweedfs
1
0
Fork 0
mirror of https://github.com/seaweedfs/seaweedfs.git synced 2024-01-19 02:48:24 +00:00
Code Issues Projects Releases Wiki Activity

Updated Overview (markdown)

Dave Cottlehuber 2020-12-09 21:31:48 +00:00
parent 21d3da2b4c
commit 7c6b0a24ed
1 changed files with 6 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
Overview.md

@ -4,7 +4,9 @@ seaweedfs comprises 3 main conceptual components. The master service and the vol
## master service ## master service
The essential master service works smart, not hard. It represents a raft cluster of 1 (or 3 or more servers) that own a consistent view of the entire seaweedfs cluster and communicate it to all participating nodes, through a raft Leader. The essential master service works smart, not hard.
It represents a raft cluster of 1 (or 3 or more servers) that own a consistent view of the entire seaweedfs cluster and communicate it to all participating nodes, through a raft Leader.
The number of servers in the master service must always be odd, to ensure that a majority consensus can be formed. You're best off keeping this number down, a small number of stable servers is better than a large pool of flakey boxes. 1 or 3 is typical. The number of servers in the master service must always be odd, to ensure that a majority consensus can be formed. You're best off keeping this number down, a small number of stable servers is better than a large pool of flakey boxes. 1 or 3 is typical.
@ -24,7 +26,9 @@ Each volume server sends periodic heartbeats with status and volume information
## filer service ## filer service
The optional filer service does heavy lifting so you don't have to. It translates seaweedfs volumes and objects, into user-visible paths (like URLs or file systems) over HTTP or UNIX FUSE mounts. The optional filer service does heavy lifting so you don't have to.
It translates seaweedfs volumes and objects, into user-visible paths (like URLs or file systems) over HTTP or UNIX FUSE mounts.
While it is not as efficient as the direct object store, it provides a convenient and common abstraction that can be used to provide normal looking filesystems, or web APIs for down/uploads, to existing applications without modification. While it is not as efficient as the direct object store, it provides a convenient and common abstraction that can be used to provide normal looking filesystems, or web APIs for down/uploads, to existing applications without modification.