Pause and Resume a Cluster
Pause a cluster when it is not needed for a period of time. Pausing stops the cluster from processing requests and stops compute charges, while the cluster's cache capacity remains reserved and billed. Resume the cluster before sending work to it, or enable Auto-suspend to suspend an idle cluster and resume it automatically when new workload arrives.
Before you begin
- Before pausing a cluster, confirm that it has no active workload. A paused cluster cannot process requests.
- A paused cluster retains its cache capacity. Cache charges continue while the cluster is paused.
Pause a cluster manually
- Log in to the VeloDB Cloud console.
- In the upper-left corner, select the warehouse that contains the cluster.
- In the left navigation pane, under Compute, click Clusters.
- On the card of a running cluster, click Pause.
The cluster status changes to Pausing. When the operation finishes, the status changes to Paused. The cluster cannot process requests while it is paused.
Resume a cluster manually
- On the Clusters page, find the paused cluster.
- Click Resume.
- In the confirmation dialog, review the restored compute resources, retained cache, and renewed charges. Click OK.
The status changes to Resuming while VeloDB Cloud restores the compute resources and mounts the retained cache. When the status changes to Running, the cluster can process requests and compute charges resume.
Configure automatic suspension
Enable Auto-suspend when the cluster should stop after idle periods but resume as soon as new workload arrives.
- On the Clusters page, click the cluster card to open its details page.
- Click Set Auto-suspend.
- Enable the Auto-suspend switch.
- Next to Idle duration, click the Edit icon, then set the number of minutes that the cluster must remain inactive before it automatically suspends.
- Review the Auto Resume Trigger Condition.
With the default settings, the cluster suspends after more than 30 minutes of inactivity. The resume mode is Automatic, so the cluster resumes when new workload arrives.
Next steps
- Warm up a resumed cluster before it receives production traffic.
- Scale a cluster when workload demand changes.
- Review cluster billing to understand compute and cache charges.