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

grammatical tweaks

Dave Cottlehuber 2020-12-27 14:41:53 +00:00
parent 6142723e34
commit 272a2ce560
1 changed files with 25 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

33
Production-Setup.md

@ -1,6 +1,6 @@
The simple setup could be deceptive. Going to production needs more complicated setup.
There are multiple layers of components. Please follow the steps to set them up from bottom up, one by one.
A robust production setup requires more configuration -- and care -- than the
[[Getting Started]] guide. There are multiple layers of components. Please follow
the steps to set them up from bottom up, one by one.
* Setup object storage
* Setup Masters
@ -14,7 +14,8 @@ And then, choose the component you want to setup
* Setup FUSE mount
* Cluster Maintenance
## Prerequisite
## Prerequisites
Make sure the ports are open. By default
| server | http port | gRPC port |
@ -24,10 +25,19 @@ Make sure the ports are open. By default
| Filer | 8888 | 18888 |
| S3 | 8333 | |
### For single node setup
You can just use `weed server -filer -s3 -ip=xx.xx.xx.xx`, to have one master, one volume server, one filer, and one S3 API server running.
If you have multi-homed servers (many IP addresses and interfaces), you need
to ensure SeaweedFS uses the correct IP, for cluster communication. Append
`-ip=123.45.67.89` to specify the appropriate address.
It is better to have several volumes running on one machine, so that if one volume is compacting, the other volumes can still serve read and write requests. The default volume size is 30GB. So if your server does not have multiple 30GB empty spaces, you need to reduce the volume size.
### For single node setup
You can just use `weed server -filer -s3 -ip=xx.xx.xx.xx`, to have one master,
one volume server, one filer, and one S3 API server running.
It is better to have several volumes running on one machine, so that if one
volume is compacting, the other volumes can still serve read and write requests.
The default volume size is 30GB. So if your server does not have multiple 30GB
empty spaces, you need to reduce the volume size.
```
weed server -filer -s3 -ip=xx.xx.xx.xx -volume.max=0 -master.volumeSizeLimitMB=1024
@ -56,12 +66,17 @@ weed master -mdir=/data/seaweedfs/master -peers=ip1:9333,ip2:9333,ip3:9333 -ip=i
```
Additional notes:
* Depending on the available disk space on each volume server, the master may need to reduce maximum volume size, e.g., add `-volumeSizeLimitMB=1024`. This will ensure each volume has several volumes.
* Depending on the available disk space on each volume server, the master may need
to reduce maximum volume size, e.g., add `-volumeSizeLimitMB=1024`. This will ensure
each volume has several volumes.
* Since it is for production, you may also want to add `-metrics.address=<Prometheus gateway address>`. See [[System Metrics]].
### Add volume servers
Adding volume servers is easy. Actually this is much easier than most other systems.
If you do not specify `-max=0` then the number of volumes is limited to 28. You can
specify a non-zero value, if you wish to explicitly manage your disk space.
* **For machine with one disk to use**
@ -94,7 +109,9 @@ Additional notes:
* After adding volume servers, there will not be data rebalancing. It is generally not a good idea to actively rebalance data, which cost network bandwidth and slows down other servers. Data are written to new servers after new volumes are created on them. You can use `weed shell` and run `volume.balance -force` to manually balance them.
## Check the object store setup
Now the object store setup is completed. You can visit `http://<master>:9333/` to check it around.
* Make sure the Free volume count is not zero.
* Try to assign some file ids to trigger a volume allocation.