gitlab-com-seaweedfs/seaweedfs
1
0
Fork 0
mirror of https://github.com/seaweedfs/seaweedfs.git synced 2024-01-19 02:48:24 +00:00
Code Issues Projects Releases Wiki Activity

Updated Mount (markdown)

Chris Lu 2020-02-26 18:22:55 -08:00
parent fab3a81f17
commit 9128f6fb91
1 changed files with 11 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
Mount.md

@ -26,9 +26,19 @@ weed mount -filer=localhost:8888 -dir=~/folder_on_seaweedfs -filer.path=/home/ch
Now you can operate the SeaweedFS files, browsing or modifying directories and files, in local file system.
To unmount, just shut it down the "weed mount".
#### Mount outside of a SeaweedFS cluster
Besides connecting to filer server, `weed mount` also directly connects to volume servers directly for better performance. However, if the SeaweedFS cluster is started by Kubernetes or docker-compose, the volume servers only knows its own IP addresses inside the cluster, which are not accessible by `weed mount`.
`weed mount -outsideContainerClusterMode` option can help here. It assumes:
* All volume server containers are accessible through the same hostname or IP address as the filer.
* All volume server container ports are open external to the cluster.
So the `weed mount -outsideContainerClusterMode -filer=<filerHostname:filerPort>` will use the filer server's hostname to replace volume servers' hostname, but keeping the volume servers' port number unchanged.
### Weed Mount Architecture
"weed mount" has a persistent client connecting to Master, to get the location updates of all volumes.
`weed mount` has a persistent client connecting to Master, to get the location updates of all volumes.
There are no network round trip to lookup the volume id location.
For reads: