mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2026-11-19 19:03:54 +01:00
Updated Filer Active Active cross cluster continuous synchronization (markdown)
1 parent
29c967d5ec
commit
59137f6624
1 file changed
+1
-1
@@ -77,7 +77,7 @@ cluster1 <-- filer.sync --> cluster2 -- filer.sync --> cluster3 -- filer.sync -
|
||||
|
||||
By default, `filer.sync` will upload files directly to volume servers. This is the most efficient way to avoid extra hops and distribute the network traffic.
|
||||
|
||||
However, it uses volume server IP addresses configured for the cluster. These IPs may not be accessible to the `filer.sync` cause of network configuration (for example cluster1 and cluster2 are on different hosting providers). In this case, it could be useful to use the `filerProxy` option to make `filer.sync` does all the transfers through the filer. In order to enable this option, `-a.filerProxy` or/and `-b.filerProxy` can be added to the `weed filer.sync` process starting command line.
|
||||
However, it uses volume server IP addresses configured for the local cluster. `filer.sync` is usually cross network. These IPs may not be accessible to the `filer.sync` because of network configurations (for example cluster1 and cluster2 are on different hosting providers). In this case, it could be useful to use the `filerProxy` option to make `filer.sync` does all the transfers through the filer. In order to enable this option, `-a.filerProxy` or/and `-b.filerProxy` can be added to the `weed filer.sync` process starting command line.
|
||||
|
||||
## Debug log
|
||||
To see all detail of transfers executed by `filer.sync`, options `-a.debug` or/and `-b.debug` can be added to the `weed filer.sync` process starting command line.
|
||||
|
||||
Reference in new issue
Block a user