FAQ - What is the procedure to skip the outstanding XDR requests on Aerospike versions 5.0 and above?

FAQ - What is the procedure to skip the outstanding records to be shipped by XDR on Aerospike versions 5.0 and above?

Detail

Before Aerospike version 5.0, XDR had the option to skip outstanding requests being shipped to a remote destination cluster. It was achieved with the command shown below:

asinfo -v 'xdr-command:skip-outstanding'

However, this command is not available in Aerospike 5 and above as the XDR architecture has changed and the digest log, to which the skip outstanding refers to, is no longer present.

It may be desirable, in certain circumstances, to use the skip outstanding functionality, for instance to avoid propagating incorrectly inserted data or to avoid going into recovery after a long outage, in this case, what is the analogue to skip outstanding in Aerospike 5 and higher?

Answer

In Aerospike 5 and above, outstanding records to be shipped by XDR can be skipped by dynamically disabling the DC/namespace.

To disable only a namespace, the below command can be used:

asadm -e "asinfo -v 'set-config:context=xdr;dc=<dcname>;namespace=<nsname>;action=remove'"

To dynamically delete a DC, which removes all the associated namespace-level configurations of that DC, use the following command:

asadm -e "asinfo -v 'set-config:context=xdr;dc=<dcname>;action=delete'"

The disassociated DC/namespace can be added back whenever required. Refer to this article for details on dynamically re-enabling shipping to the DC.

Keywords

XDR 5.X SKIP OUTSTANDING

Timestamp

March 2021

© 2021 Copyright Aerospike, Inc. | All rights reserved. Creators of the Aerospike Database.