Updated FUSE Mount (markdown)

FUSE-Mount.md

@@ -37,6 +37,36 @@ the volume servers only knows its own IP addresses inside the cluster,
 `weed mount -outsideContainerClusterMode` option can help here. It assumes all volume server containers are accessible 
 through the `publicUrl` address when starting with `weed volume -publicUrl=xxx`.
 
+#### Multiple mounts with multiple Filers of a SeaweedFS cluster
+
+If there are multiple filers in a SeaweedFS cluster, whether the filers share the same filer store or not, they need to be started with
+`weed filer -peers=filer1:port1,filer2:port2,filer3:port3`.
+
+This is to ensure the updates from one filer can be transferred to the other filers. The filers would not be constantly querying the 
+filer stores for updates. Instead, the filers will listen to each other for updates, which is more efficient.
+
+So for the following topology, the updates from one mount can be propagated to other mounts. 
+
+```
+
+mount1 ---> filer1 ---> filer2 ---> mount2
+                |
+                +-----> filer3 ---> mount3
+```
+
+However, in most cases, one filer should be enough, since the mount will only get asynchronous metadata updates to filer,
+and will read and write to the volume servers directly, one filer should be enough to handle most of the work.
+
+```
+
+filer ---- mount1
+   |
+   +------ mount2
+   |
+   +------ mount3
+
+```
+
 ### Weed Mount Architecture
 
 `weed mount` has a persistent client connecting to Master, to get the location updates of all volumes.