Besides Couchbase Web Console, you can use several Couchbase REST-API endpoints to modify XDCRsettings. Some of these settings are references used in XDCR and some of these settings will change XDCR behavior or performance:
Viewing, setting and removing destination cluster references, can be found in Section 8.9.1, “Getting a Destination Cluster Reference”, Section 8.9.2, “Creating a Destination Cluster Reference” and Section 8.9.3, “Deleting a Destination Cluster Reference”.
Creating and removing a replication via REST can be found in Section 8.9.2, “Creating a Destination Cluster Reference” and Section 8.9.3, “Deleting a Destination Cluster Reference”.
Concurrent replications, which is the number of concurrent replications per Couchbase Server instance. See Section 8.9.6, “Viewing Internal XDCR Settings”.
For the XDCR retry interval you can provide an environment
variable or make a PUT request. By default if XDCR is unable to
replicate for any reason like network failures, it will stop and
try to reach the remote cluster every 30 seconds if the network
is back, XDCR will resume replicating. You can change this
default behavior by changing an environment variable or by
changing the server parameter
xdcr_failure_restart_interval with a PUT
By an environment variable:
shell> export XDCR_FAILURE_RESTART_INTERVAL=60
By server setting:
shell> curl -X POST http://Administrator: <http://Administrator/>email@example.com:9000/diag/eval \ -d 'rpc:call(node(), ns_config, set, [xdcr_failure_restart_interval, 60]).'
You can put the system environment variable in a system configuration file on your nodes. When the server restarts, it will load this parameter. If you set both the environment variable and the server parameter, the value for the environment parameter will supersede.