This page outlines how to expand your ClustrixDB cluster using the Private AMI.
If you have deployed a cluster using the Private AMI, you must continue to use the Private AMI to expand your cluster.
This can be requested here or by contacting Clustrix Support. The AMI should be for the appropriate AWS region and be the same as the version of ClustrixDB that your database is currently running.
You may have initially provisioned your cluster using a different AMI, then upgraded to a newer version. For expanding your cluster, Clustrix recommends using the AMI for the version currently in use.
Ensure that the instances use the same configuration options as your current cluster, including:
If you are expanding your cluster, you may need a license for more cores or nodes. Before expanding your cluster, update your license key in the WebUI or at the command line:
sql> set global license = 'license_key_including_braces';
After each new node has been prepared using the step above, you are now ready to expand your cluster's capacity.
Congratulations, your cluster has been successfully expanded. At this time, your new nodes are part of your cluster and available to service queries, but do not yet contain data. The ClustrixDB Rebalancer will work in the background to move data onto the new node(s). To monitor this process, refer to the instructions regarding Managing the Rebalancer.