Modify an Aerospike Cloud database cluster
You can perform any of the following operations – in the Cloud Console or using the APIs – to change a database cluster after it it has been provisioned.
- Scale the database cluster – change the number of nodes in the cluster or modify the instance type of the nodes.
- Modify the database cluster configuration – use the advanced configuration page to tune performance or modify the behavior of your database cluster.
- Decommission the database cluster – delete the cluster and the AWS resources it is consuming.
Scale a database cluster
-
Navigate to the database clusters page.
Click Scale cluster (crossed arrows icon) to open a page where you can change the instance type and node count of the database cluster.
-
Set your new cluster size. The size can only be changed in increments that balance evenly across the number of zones in the cluster.
-
Review and submit the change
Finalize your selections and submit the modification. Scaling operations take time to implement and are done sequentially. It may take some time before your cluster matches the state you have requested. The Console will show the desired state and a status of
Updatingto reflect that a change is being made to reach the state you have requested.
-
Create a Cloud API Key and retrieve a bearer token
See Using Cloud APIs to learn about creating a key to use with the API.
-
Make a PATCH request with the desired database spec.
The following example is a general command to modify your cluster:
Terminal window curl -X PATCH "https://api.aerospike.cloud/v2/databases/<database-id>" \-H "Authorization: Bearer <bearer-token>" \-H "Content-Type: application/merge-patch+json" \--data '{"aerospikeCloud":{"clusterSize":4}}'
Modify the database cluster configuration
-
Navigate to the clusters page.
Click Edit server config (pencil icon) to open the advanced configuration page.
-
Enter new advanced configuration options.
See advanced configuration for information about what you can change. Some operations are risky, and combining different operations can severely degrade or halt your cluster. Be careful when making changes that are not recommended.
-
Review and submit the change.
Finalize your selections and submit the modification. It may take some time before your cluster matches the state you have requested. The Console will show the desired state and a status of
Updatingto reflect that a change is being made to reach the state you have requested.
-
Create a Cloud API Key and retrieve a bearer token.
See Using Cloud APIs to learn about creating a key to use with the API.
-
Make a PATCH request with the desired database spec.
The following example is a general command to patch your cluster:
Terminal window curl -X PATCH "https://api.aerospike.cloud/v2/databases/<database-id>" \-H "Authorization: Bearer <bearer-token>" \-H "Content-Type: application/merge-patch+json" \--data '{"aerospikeServer":{"default-ttl":30,"nsup-period":60}}'
Decommission the database cluster
-
Navigate to the database clusters page.
Click Decommission cluster (trash can icon). The cluster name disappears immediately from the list of active clusters. To retrieve metadata about a decommissioned database cluster, use the toggle to display decommissioned clusters.
-
Create a Cloud API Key and retrieve a bearer token.
See Using Cloud APIs to learn about creating a key to use with the API.
-
Make a DELETE request with the desired database cluster ID. For example:
Terminal window curl -X DELETE "https://api.aerospike.cloud/v2/databases/<database-id>" \-H "Authorization: Bearer <bearer-token>"