Updated Filer Active Active cross cluster continuous synchronization (markdown)

Chris Lu 2021-08-09 22:59:01 -07:00
parent 994c231cf4
commit 29c967d5ec

@ -75,10 +75,12 @@ cluster1 <-- filer.sync --> cluster2 -- filer.sync --> cluster3 -- filer.sync -
## Filer Proxy
By default, filer.sync will upload files directly on master and volumes, it uses IP configured in the filer. These IPs could 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.
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.
## 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.
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.
## Limitations