Resize a Astra DB Classic database
Scale up databases to increase capacity.
If a database is growing quickly or exceeding capacity, add another capacity unit (CU) to expand the storage and capabilities of the database.
Scaling considerations
|
Scaling up has billing implications. Scaling down is not supported. For assistance with scaling down, contact DataStax Support. |
-
Scaling up has billing implications.
-
Only a database owner can resize a database.
-
You can’t scale down databases.
-
You can’t resize databases running on the Developer tier.
-
You can’t modify the compute size of existing databases.
Scale up a database
You can increase a database by a maximum of three CU at a time. You can resize a database multiple times if you need additional CUs. A database can’t have more than 20 CUs total.
-
Astra Portal
-
DevOps API
-
In the Astra Portal, go to Databases.
-
Locate the database that you want to scale up, click More, and then select Expand CUs.
-
Modify the number of CUs for the database.
The total amount of storage and estimated cost changes dynamically based on the number of CUs entered.
-
To start resizing the database, click Expand, and then click Yes to confirm the increase.
Use the DevOps API to resize a Astra DB Classic database:
curl -sS --location -X POST "https://api.astra.datastax.com/v2/databases/DATABASE_ID/resize" \
--header "Authorization: Bearer APPLICATION_TOKEN" \
--header "Content-Type: application/json"
--data '{
"capacityUnits": TOTAL_CAPACITY_UNITS
}'Replace the following:
-
DATABASE_ID: The database ID. -
APPLICATION_TOKEN: An application token with the Database Administrator role. -
TOTAL_CAPACITY_UNITS: The desired total number of capacity units, including the database’s existing capacity units. For example, if the database has 3 CUs and you want to increase to 5 CUs, enter5.
The database enters Resizing status while scaling up. Database administration is limited in Resizing status, but reads and writes generally aren’t impacted. Traffic spikes or increased capacity demands might be slower than usual while replication and resizing are in progress. While scaling takes little time, it can take some time (potentially hours) for replication and resizing to complete. Once resizing is complete, the database returns to Active status.
