From 87c5c288d191b1a2f50f4d573eb7427927b90936 Mon Sep 17 00:00:00 2001 From: Chris Lu Date: Sun, 7 Nov 2021 14:54:31 -0800 Subject: [PATCH] Updated Filer Store Replication (markdown) --- Filer-Store-Replication.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Filer-Store-Replication.md b/Filer-Store-Replication.md index 0c53f37..819e142 100644 --- a/Filer-Store-Replication.md +++ b/Filer-Store-Replication.md @@ -10,6 +10,8 @@ How is it possible? When a filer starts up, it will report itself to the master. So the master knows all the filers. It will keep each filer updated about its peers (since version 2.77). +So when a filer was added or removed from the cluster, there is no configuration change needed. This makes rolling-restart much easier, and filer instances in Kubernetes can run in ReplicaSet instead of StatefulSet. + # Metadata synchronization Knowing all the peers, one filer will keep its own metadata updated: