Skip to main content

Change database resource configurations

Cluster resources are the flavor (vCPU and RAM), the data disk size, and the storage policy that sets IOPS. All three can be changed while the cluster is running, within your available quota.

View current resources​

On the menu bar, select Database Platform → All Database or Non-Relational Database → click the Cluster ID → select the Resource tab.

Two figures are shown:

  • Current Resource — the cluster's configuration today: vCPU, RAM, data disk size.
  • Available Resource — the ceiling you can scale to, from your quota.

Check Available Resource before planning a change. Exceeding it is the most common reason an update is rejected.

Adjust compute and disk​

  1. On the Resource tab, click Edit Resource — the pencil icon next to Database Resources.

  2. Make your changes:

    • Compute — select a different Flavor to change vCPU and RAM.
    • Data disk — enter a larger value in Data disk size (GB).

  3. Click Update.

The cluster status changes to Resizing, returning to Running when done. The process takes 5–10 minutes; avoid other operations during it.

warning

Three constraints worth knowing before you start:

  • Quota is a hard limit. A configuration exceeding Available Resource is rejected with an error.
  • Data disk size cannot be reduced. You can only increase it. There is no path back short of restoring into a new cluster.
  • Reducing compute restarts the cluster. Lowering vCPU or RAM automatically restarts the database engine to apply the change, dropping connections.

Adjust the storage policy​

The storage policy determines I/O performance and cost.

  1. On the Resource tab, click Edit Storage Policy — the pencil icon next to Storage Policy.
  2. Select a new policy matching your workload.
  3. Click Update.

This also takes 5–10 minutes. Do not perform other operations while it runs.

tip

For production, use a storage policy of at least 4,000 IOPS. Below that, performance becomes the bottleneck well before compute does, and adding vCPU will not help.

Next steps​