Downgrade Option for Managed Databases
h
hris
Please add this ASAP
W
Whitney Jutzin
Merged in a post:
Allow to resizing down MySQL database
Shahrun Nadzree
Right now theres no option to resizing down the managed MySQL database. Previously we can do it using doctl but that has been disabled. This is very useful for us as we only will upgrade during peak season.
W
Whitney Jutzin
Merged in a post:
Allow Postgres Downscaling
Andrii Chaika
Right now, you can pick only instances with SSD size >= from the current one.
The issue is that sometimes you need more CPU, sometimes you need more RAM. If you ever happened to use Space optimized droplets there is no way you can scale back for reasonable money. You may need less CPU at one point in time. There are lots of scenarios when you really need it.
My proposal is to allow downscaling of instances automatically.
Right now you can achieve it by creating a new smaller DB and migrating all data from the old one.
I think it can be fairly easily implemented in a managed manner (just create a new, smaller instance, migrate data, destroy old instance)
You may put a condition that the new instance must have enough space to accommodate current disc usage +30% for safety reasons.
W
Whitney Jutzin
Merged in a post:
Allow downgrading Postgres databases to smaller disk
Andrii Chaika
My database uses 10% of disk. I was using higher tier because of high load I experienced in the past. I want to downgrade it to lower tier but it is not possible.
DigitalOcean supports live migration between databases. I want you to allow downgrading database if there is enough disk space on lower tier.
For example I have 580GB with 10% disk utilization. I want to downgrade to 240GB instance. It has plenty of space.
You can put a limit for example that the database size must be less than 80% of total disk space of lower tier.
Jane Alam Jan
Same here, I only need to upgrade for special events, when the load becomes higher. The overhead is too high to downgrade i.e create a new instance, migrate, change connections.
Even if it's an offline operation, it's fine. As long as the same connection parameters can be used and don't require a cluster wide deployment.
Luiz Louro
Hi, my company also needs this feature. I was used to do that in other Cloud Providers, it is really useful when we have campaigns or something that will create spikes that will require more CPF or memory.
Rene Hermenau
Please, prioritize it. Either that or at least give the option to do replication and migration to another managed db instance to be able to migrate a managed db instance without any downtime.
We switched to DO managed db to not have to maintain and implement replication over different servers but now while we are in production we noticed we are locked in and can not switch our data to another db instance without having a write lock on our application.
This is a very unpleasant situation and the first time in years we are considering leaving digitalocean because of it.
R
Rohan Jayasekera
I see that in Settings the dropdown for server size does list smaller sizes, but they're greyed out because "Disk must be at least the same size". So maybe a downgrade option does exist in theory, but what's really missing is the option to upgrade CPU+RAM while keeping the same SSD size – just like droplets have. This would allow us to upgrade in place and later downgrade in place, which is currently impossible. (BTW it seems odd to me that CPU+RAM are tied to disk size. A small database might have lots of activity, and a large database might have little activity.)
P
Patrick M
Yes, this would be huge. As is, the only way to do this results in like 30 minutes of downtime while I export and import my data.
Artyom Kazak
Same here — and it's not even possible to set up a continuous migration between two DO-managed postgres clusters.
Right now I'm paying 4x more for my database than I need, just because I had a traffic spike
once
. This is not great.Load More
→