Network and System Outages
XDCR is resilient to intermittent network failures. In the event that the destination cluster is unavailable due to a network interruption, XDCR will pause replication and will then retry the connection to the cluster every 30 seconds. Once XDCR can successfully reconnect with a destination cluster, it will resume replication. In the event of a more prolonged network failure where the destination cluster is unavailable for more than 30 seconds, a source cluster will continue polling the destination cluster which may result in numerous errors over time. In this case, you should delete the replication in Couchbase Web Console, fix the system issue, then re-create the replication. The new XDCR replication will resume replicating items from where the old replication had been stopped.
Your configurations will be retained over host restarts and reboots. You do not need to re-configure your replication configuration in the event of a system failure.
XDCR does not replicate views and view indexes; you must manually exchange view definitions between clusters and re-generate the index on the destination cluster.
Non UTF-8 encodable document IDs on the source cluster are automatically filtered out and logged and are not transferred to the remote cluster.
Flush requests to delete the entire contents of bucket are not replicated to the remote cluster. Performing a flush operation will only delete data on the local cluster. Flush is disabled if there is an active outbound replica stream configured.