Updated Filer Store Replication (markdown)

Chris Lu 2021-11-07 18:49:43 -08:00
parent 87c5c288d1
commit 18bccce200

@ -12,6 +12,8 @@ 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.
# Metadata synchronization
Knowing all the peers, one filer will keep its own metadata updated: