How can I downgrade my DB cluster

Hi @ALKateb,

EDIT April 2023

As of the time being Managed Database Cluster cannot be resized to an instance with smaller disks.

The main reason why database nodes cannot be resized to smaller sizes is due to the risk of data loss. This is also valid for our Droplets as well.

To downgrade to a smaller instance you can follow the steps here:

• Create a new Managed database cluster with the desired size
• Migrate your data from the old large instance to the new small instance
• Update your applications to use the new Managed database cluster
• Check the database activity for your old large instance and only once you are certain that the instance is no longer used, can you go ahead and destroy it.

In the past, you could use the API to downgrade your instances as described bellow which is currently not the case.

---

At the moment Digitalocean does not support scaling down of a Managed database cluster from the UI, You can read about limitations here:

https://docs.digitalocean.com/products/databases/mysql/#limits

Alternatively, you can resize the database cluster to size your choice using DO API/DOCTL CLI.

DOCTL CLI:

https://docs.digitalocean.com/reference/doctl/reference/databases/resize/

doctl databases resize b1723184-32d7-41eb-8bb3-f911b6d9d449 --num-nodes 1 --size db-s-1vcpu-1gb

DO API:

https://developers.digitalocean.com/documentation/v2/#resize-a-database-cluster

Please note, there are 3 different slugs identifiers for machine type. You have to modify them according to your cluster resize slug size. For example 

Basic Node :
{"size":"db-s-2vcpu-4gb", "num_nodes":1}

General Purpose Node :
{"size":"gd-4vcpu-16gb", "num_nodes":1}

Storage Optimized Node :
{"size":"so1_5-4vcpu-32gb", "num_nodes":1}

curl -X PUT -H "Content-Type: application/json" -H "Authorization: Bearer xxxxxx" -d '{"size":"gd-4vcpu-16gb", "num_nodes":1}' "https://api.digitalocean.com/v2/databases/{UUID}/resize"

I hope this helps!

Regards, Rajkishore