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:31:10 +00:00
parent 3bf1b5536a
commit 86a661857f
1 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
Components.md

@ -1,6 +1,6 @@
# SeaweedFS Components
SeaweedFS comprises of 3 main conceptual components. The master service and the volume service together provide a distributed object store, with user-configurable replication and redundancy. The optional filer and S3 service are additional layers on top of the object store. Each of these services may run as one or separate instances, on various actual servers.
SeaweedFS comprises 3 main conceptual components. The master service and the volume service together provide a distributed object store, with user-configurable replication and redundancy. The optional filer and S3 service are additional layers on top of the object store. Each of these services may run as one or separate instances, on various actual servers.
## Master service
@ -40,16 +40,16 @@ This optional service provides AWS style S3 buckets, similar to the filer servic
The volume in SeaweedFS means a single actual file consists of many small files. When master starts, it configures the volume file size, default to 30GB. At the beginning, there are 8 volumes created.
Each volume has its own TTL, replication.
Each volume has its own TTL and replication.
## Collection Concept
One collection is basically a group of volumes. If no volume in the collection, the volumes will be auto created.
One collection is basically a group of volumes. Initially, if no volume is present within the collection, the volumes will be auto created.
The TTL and replication options are for each volume, not for the collection. One collection can have volumes of different TTL or replication options.
The collection can be deleted quickly, since it is just simply removing all the volumes in the collection.
If you want to use S3 service, one bucket has a dedicated collection. So removing a bucket is also fast.
If you want to use S3 service, each bucket has a dedicated collection. So removing a bucket is also fast.
Since one collection needs to have several volumes, and each volume is 30GB by default, you may run out of disk space quickly. You can reduce the volume size to 1GB or 512MB.
Since one collection needs to have several volumes, and each volume is 30GB by default, you may run out of disk space quickly. You can reduce the volume size to 1GB or 512MB, to work around this restriction.