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 Production Setup (markdown)

Chris Lu 2020-04-09 00:15:00 -07:00
parent a87fb430c2
commit 34f84a6f15
1 changed files with 8 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
Production-Setup.md

@ -12,6 +12,7 @@ There are multiple layers of components. Please follow the steps to set them up
And then, choose the component you want to setup
* Setup S3
* Setup FUSE mount
* Cluster Maintenance
## Prerequisite
Make sure the ports are open. By default
@ -145,6 +146,13 @@ Run
* `-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.
## Cluster Maintenance
In a cluster, volume servers can go down. But automatic rebalancing will be problematic. It can cause unexpected busy network activities. For example, the heartbeat of a volume server may come and go, causing unnecessary busy system. Current recommended strategy is to keep existing data readonly, and automatically add new writable volumes.
There are `volume.balance` and `volume.fix.replication` commands in `weed shell`. You can configure them to run during off hours.
See [[Volume Management]] for details.
## Other
* Setup metrics, see [[System Metrics]]