Updated Filer Store Replication (markdown)

Chris Lu 2021-11-07 14:54:31 -08:00
parent 066be6a2e7
commit 87c5c288d1

@ -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: