From 7c6b0a24ed8a20f886edbf20cb9846c907f3bdcf Mon Sep 17 00:00:00 2001 From: Dave Cottlehuber Date: Wed, 9 Dec 2020 21:31:48 +0000 Subject: [PATCH] Updated Overview (markdown) --- Overview.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/Overview.md b/Overview.md index c6770fd..b229585 100644 --- a/Overview.md +++ b/Overview.md @@ -4,7 +4,9 @@ seaweedfs comprises 3 main conceptual components. The master service and the vol ## 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. @@ -24,7 +26,9 @@ Each volume server sends periodic heartbeats with status and volume information ## 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.