Articles in this section

Why is XDR pre-5 DC-STATE not changing?

Detail

When testing XDR, remote data centers are shut down and while tend requests are seen to be failing, the dc-state of the remote data center is not listed as CLUSTER_DOWN.

Answer

This is expected behaviour when there are no records being sent to the remote DC. When Aerospike starts, XDR tries to issue tend requests to the remote cluster and reports an error if these fail. XDR does not initiate a full healthcheck until there are writes being sent from the source DC to the remote DC. As there are no writes, there is no need to start a window shipper process and therefore it is not necessary to determine an exact status for the remote cluster.

Notes

XDR is behaving as designed. If there is no data to ship and no writes are failing, the dc-state is not relevant.

Applies To Earliest Version

Pre 4.9

Applies To Latest Version

4.9
Was this article helpful?
0 out of 0 found this helpful