Validated on 28 Jun 2021 • Last edited on 18 Dec 2024
MongoDB is a source-available cross-platform document-oriented database program for high-volume storage. Classified as a NoSQL database program, MongoDB uses JSON-like documents with optional schemas.
You can resize existing MongoDB database clusters at any time to add more CPUs, RAM, and storage. To avoid data loss, you cannot decrease the size of database clusters.
Resize a Database Cluster Using the CLI
Note
To resize a database cluster using doctl, you need to provide a value for the --size flag, which specifies the cluster’s new configuration (number of CPUs, amount of RAM, and hard disk space). Use the doctl databases options slugs command to get a list of available values.
You can also review a list of available slugs for each engine on its pricing page.
How to Resize a Database Cluster Using the DigitalOcean CLI
To resize a database cluster using the API, you need to provide a value for the size field, which specifies the cluster’s configuration (number of CPUs, amount of RAM, and hard disk space). Use the /v2/databases/options endpoint to get a list of available values.
You can also review a list of available slugs for each engine on its pricing page.
How to Resize a Database Cluster Using the DigitalOcean API
To resize a MongoDB database cluster, click the name of the cluster in the control panel to go to its Overview page, then click the Settings tab.
You cannot reduce the amount of storage in a cluster below the amount of storage you are currently using in your cluster.
To switch to a database cluster plan with less storage, fork the cluster and select a smaller database cluster plan for the new cluster.
In the Cluster configuration section, click Edit. Select your cluster configuration and CPU option.
You can also select your storage size.
Once you have selected your new configuration and size, click Save to provision the new configuration. The provisioning takes several minutes but the total time depends on the size of the cluster.
Your cluster’s state changes from Active to Resizing until the process is done. You can expect no downtime and do not need to take action.