mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2024-01-19 02:48:24 +00:00
Updated Filer Store Replication (markdown)
parent
f30e537390
commit
72f2276c1a
|
@ -34,7 +34,9 @@ So aggregating metadata updates form its peers is required when the filers are u
|
|||
|
||||
If the filer is running on embedded store, the metadata updates from its peers would be saved locally.
|
||||
|
||||
This basically synchronize the metadata across all the filer stores. If filers are using shared filer stores, this is optional.
|
||||
This basically synchronize the metadata across all the filer stores, where every filer store will have a full copy of all the metadata.
|
||||
|
||||
This also naturally replicated the filer store to achieve high availability for metadata.
|
||||
|
||||
# Example Topologies
|
||||
|
||||
|
@ -57,7 +59,7 @@ filer1(leveldb) <-> filer2(leveldb)
|
|||
filer1(leveldb) <-> filer2(rocksdb)
|
||||
```
|
||||
|
||||
* Two filers with one shared stores are fine.
|
||||
* Two filers with one shared store instance are fine.
|
||||
|
||||
```
|
||||
filer1(mysql) <-> filer2(mysql)
|
||||
|
@ -65,6 +67,7 @@ filer1(mysql) <-> filer2(mysql)
|
|||
|
||||
* Two filers with a shared store and an embedded store are NOT fine.
|
||||
|
||||
This is because the `filer2` here will not attempt to persist `filer1` metadata updates to its mysql store.
|
||||
```
|
||||
filer1(leveldb) <--XX NOT WORKING XX---> filer2(mysql)
|
||||
```
|
||||
|
|
Loading…
Reference in a new issue