Dynamically decrease the number of connector instances

You can dynamically remove connector instances from the change-notification system. You remove connector instances that you dynamically added with the asinfo command by running this command again, but with action set to remove.

To find out which connector instances are active, run the asadm command info xdr for <dc>, where <dc> is the name of the XDR datacenter to which the nodes running the connector instances belong. The command lists these nodes.

Stop sending change notifications

To stop your Aerospike cluster from sending change notifications to a connector instance, run the following command, where DC is the name of the XDR datacenter where the node running the connector instance is located, and IP-ADDRESS is the IP address of the node:

asinfo -v "set-config:context=xdr;dc=DC;node-address-port=IP-ADDRESS;action=remove"

Result

If the node was added to its XDR datacenter dynamically with the asinfo -v "set-config:context=xdr;dc=<dc>;node-address-port=<IP-address>;action=add" command, the node is removed from memory after you run the command.

If the node is listed in the xdr stanza of the Aerospike configuration file, the node is still listed there after you run the command. However, the Aerospike cluster no longer sends change-notifications to it until the cluster is restarted. The connector instance continues to run on this node unless you stop it.

Caution

Before the hotfix updates for Aerospike Database released on June 25, 2024, there was a bug affecting connector scaling in XDR configurations.

Without the update, if you dynamically removed a connector from a node in an XDR configuration, you needed to restart the XDR source node in order to propagate the connector change across all XDR nodes, or otherwise risk potential update delays due to imbalanced connector distribution until restart.

The update was released for the following Database versions:

• 7.1.0.2
• 7.0.0.11
• 6.4.0.19
• 6.3.0.24
• 6.1.0.36