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

adjust wiki for filer.remote.gateway

Chris Lu 2021-09-15 22:56:58 -07:00
parent 1dfbbc587b
commit fe3153a1b4
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
Gateway-to-Remote-Object-Storage.md

@ -8,9 +8,9 @@ However,
How to synchronize them automatically?
# Design
# Design of Gateway to Remote Object Store
The `weed filer.remote.sync -createBucketAt=cloud1` process does these jobs:
The `weed filer.remote.gateway -createBucketAt=cloud1` process does these jobs:
* Local new buckets will be automatically mounted to the remote storage specified in `-createBucketAt`
* Local deleted buckets will be automatically deleted in its remote storage.
* All local changes under `/buckets` are uploaded to its remote storage.
@ -28,7 +28,7 @@ If there are some existing buckets, run this to mount all of them as local bucke
## 2. Upload local changes in `/buckets`
Start a `weed filer.remote.sync` and let it run continuously.
Start a `weed filer.remote.gateway` and let it run continuously.
If new buckets are created locally, this will also automatically create new buckets in the specified remote storage.
@ -43,7 +43,7 @@ synchronize /buckets, default new bucket creation in cloud1 ...
In some cloud storage vendor, the bucket names need to be unique. To address this, run it with `-createBucketWithRandomSuffix` option.
It will create buckets with name as `localBucketName-xxxx`, appending a random number as the suffix.
```
$ weed filer.remote.sync -createBucketAt=cloud1 -createBucketWithRandomSuffix
$ weed filer.remote.gateway -createBucketAt=cloud1 -createBucketWithRandomSuffix
```