Updated Production Setup (markdown)

Chris Lu 2020-12-08 14:43:10 -08:00
parent 0eddafa0b8
commit 9a52345187

@ -140,14 +140,13 @@ If using default embedded filer store, the metadata is not shared. The filer wil
Follow [[Amazon S3 API]] to generate a json config file, to assign accessKey and secretKey for different identities, and give read/write permissions to different buckets.
Run
Start s3 together with filer. This avoids the setup for s3 to support multiple filers.
`weed s3 -filer=<filer_host:filer_port> -config=<config.json> -port=8333`
```
weed filer -s3 -s3.config=<config.json> -port=8333
```
Alternatively, an easier way is to start s3 together with filer. This avoids the setup for s3 to support multiple filers.
`weed filer -s3 -s3.config=<config.json> -port=8333`
The s3 ip address is not needed. When running S3 related tools, remember to set the endpoint to `http://<s3_server_host>:8333`.
The endpoint is `http://<s3_server_host>:8333`.
## Setup FUSE mount
@ -157,7 +156,7 @@ Run
* `-chunkCacheCountLimit` means how many entries cached in memory, default to 1000. With default `-chunkSizeLimitMB` set to 4, it may take up to 4x1000 MB memory. If all files are bigger than 4MB.
* `-replication` is the replication level for each file. It overwrites replication settings on both filer and master.
* `-outsideContainerClusterMode` is used if running master, volume server, and filer inside a cluster, and the volume server IP addresses are not visible to FUSE clients. If so, the volume servers need to run on different ports and the ports need to be proxied through the filer IP address.
* `-outsideContainerClusterMode` is used if running master, volume server, and filer inside a cluster, and the volume server IP addresses are not visible to FUSE clients. If so, the volume servers accessed through the `publicUrl` address when starting with `weed volume -publicUrl=xxx`.
## Cluster Maintenance