From 9128f6fb91520fafbac23ccadf19f97cf43af3dc Mon Sep 17 00:00:00 2001 From: Chris Lu Date: Wed, 26 Feb 2020 18:22:55 -0800 Subject: [PATCH] Updated Mount (markdown) --- Mount.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/Mount.md b/Mount.md index 72b3d19..2cf969e 100644 --- a/Mount.md +++ b/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=` 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: