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

Created Async Replication to another Filer (markdown)

Chris Lu 2018-09-22 02:08:00 -07:00
parent dee1cce71d
commit a58f41139e
1 changed files with 54 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

54
Async-Replication-to-another-Filer.md Normal file

@ -0,0 +1,54 @@
# Architecture
![](FilerAsyncReplication.png)
# How it works
There should be two Seaweed File Systems running, possibly across data centers. Each should have its filer, master, and volume servers.
## Configuration
* Configure notification. use "`weed scaffold -config=filer`" to see the notification section.
```
[notification.log]
enabled = true
[notification.kafka]
enabled = false
hosts = [
"localhost:9092"
]
topic = "seaweedfs_filer1_to_filer2"
```
* Setup Kafka. Possibly you need to create the Kafka topic if auto topic creation is not enabled.
* Configure replication. use "`weed scaffold -config=replication`" to see the notification section.
```
[source.filer]
enabled = true
grpcAddress = "localhost:18888"
directory = "/buckets" # all files under this directory tree are replicated
[notification.kafka]
enabled = true
hosts = [
"localhost:9092"
]
topic = "seaweedfs_filer1_to_filer2"
[sink.filer]
enabled = true
grpcAddress = "localhost:18888"
directory = "/backup" # all replicated files are under this directory tree
replication = ""
collection = ""
ttlSec = 0
```
Please read the source.filer and sink.filer configurations carefully and make sure you fully understand its intention. This is actually using one filer and replicate files from one folder to another folder.
* Start the replication. "`weed filer.replicate`"