From 5e892d7a8bc6015fe2eb778af64897236437b2f6 Mon Sep 17 00:00:00 2001 From: Chris Lu Date: Sun, 7 Nov 2021 18:50:09 -0800 Subject: [PATCH] Updated Filer Store Replication (markdown) --- Filer-Store-Replication.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Filer-Store-Replication.md b/Filer-Store-Replication.md index 7b44917..5b2ce13 100644 --- a/Filer-Store-Replication.md +++ b/Filer-Store-Replication.md @@ -12,7 +12,7 @@ When a filer starts up, it will report itself to the master. So the master knows 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. -What's more, adding a fresh new filer will automatically synchronize the metadata with other filers. Resuming a paused filer will also resume the metadata synchronization from when it was stopped. Everything will just work. +What's more, adding a fresh new filer will automatically synchronize the metadata with other filers. Resuming a paused filer will also resume the metadata synchronization from when it was stopped. Everything will/should just work! # Metadata synchronization