Skip to main content

Dynamically Increasing and Decreasing the Number of Connector Instances


These instructions only apply to outbound streaming connectors (streaming data out of Aerospike).

You can dynamically increase the throughput of change-notification messages from your Aerospike database to your target system. You can do so by adding more instances of the outbound connector that you are using. Adding more instances also helps prevent traffic from slowing down excessively due to any failures of nodes on which connector instances are running.

If you find that any of the connector instances that you added dynamically are underused, you can also remove them dynamically.

For example, if you know that your Aerospike cluster has traffic spikes from time to time, you can prepare in advance to ensure that data continues to flow without bottlenecks through your connectors to your target system. You can have a number of additional connector instances configured and ready to run. Then, when traffic spikes, you can start and dynamically add them to the list of connector instances receiving change-notifications. When traffic returns to normal levels, you can dynamically remove the connector instances from that list.

You add connector instances by running the asinfo command with action set to add. This command persists the instances in memory only, and does not add them to the xdr section of the /etc/aerospike/aerospike.conf configuration file.

You remove connector instances that you added with the asinfo command by running this command again, but with action set to remove.

Example of adding a connector instance

asinfo -v "set-config:context=xdr;dc=connector;node-address-port=;action=add"

Example of removing the same connector instance

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

If you dynamically remove a connector from a node in an XDR configuration, you must restart the XDR source node in order to propagate the connector change across all XDR nodes. If you do not restart the source node, the imbalanced connector configuration is likely to cause update delays.