From f13b763552f2216c0d68a86e7c540d15f1c916c6 Mon Sep 17 00:00:00 2001 From: Chris Lu Date: Sun, 15 Nov 2026 20:52:03 -0800 Subject: [PATCH] docs: explain the 3-filer recommendation in the production setup notes (#12671) * docs: explain the 3-filer recommendation in the production setup notes Co-Authored-By: Claude Opus 5.5 * docs: note that a filer load balancer must forward the gRPC port Co-Authored-By: Claude Opus 5.5 --------- Co-authored-by: Claude Opus 5.5 --- note/slides/seaweedfs-production-setup.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/note/slides/seaweedfs-production-setup.md b/note/slides/seaweedfs-production-setup.md index 0155120b29..c174152fe8 100644 --- a/note/slides/seaweedfs-production-setup.md +++ b/note/slides/seaweedfs-production-setup.md @@ -45,6 +45,8 @@ Rule of thumb: start with 3 masters, then grow volume servers with data. - Metadata store options: PostgreSQL, MySQL, Redis, Cassandra, TiKV, etc. - Run **3 filers** for HA - Filers are stateless relative to each other — state lives in the DB +- No quorum among filers: 2 already survive one failure; the third keeps a spare while one is down for upgrades +- Give clients every filer address (e.g. `-filer=f1:8888,f2:8888,f3:8888`) or a load balancer that forwards both the HTTP and gRPC ports (8888 and 18888) **S3 Servers** @@ -77,7 +79,7 @@ Keeps housekeeping off the hot path. |----------------|----------------------|-----------------------------------| | Master | 3 | Raft quorum, topology, volume map | | Volume Server | N (scale out) | Stores data needles | -| Filer | 3 | Metadata gateway | +| Filer | 3 (2 minimum) | Metadata gateway, no quorum | | Metadata DB | HA cluster | Persists filer metadata | | S3 Server | N (by throughput) | S3 API frontend | | Admin | 1 | Background job coordinator |