Updated Filer Active Active cross cluster continuous synchronization (markdown)

Jérôme BAROTIN 2021-07-22 14:20:35 +02:00
parent a747b55e34
commit 3216679af6

@ -75,10 +75,10 @@ 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` cli.
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.
## 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` cli.
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