Pause and Resume a Cluster
Pause a cluster to release its compute resources when it is not processing workloads. The cluster cannot process requests while paused, but its cache resources and data are retained. Cache resources can continue to be metered and billed while the cluster is paused.
Resume a manually paused cluster before sending workloads to it. To pause idle clusters automatically, configure Auto-suspend.
Before you begin
- You need permission to manage compute resources in the warehouse.
- The warehouse must not be in the Creating state.
- You can pause only a Running cluster. You can manually resume only a cluster that was paused by a user.
- Before pausing a cluster, stop or redirect its active workloads. The cluster cannot process requests while pausing or paused.
- If you cannot select Pause, point to it to view the reason.
Pause a cluster
- 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.
- Select the running cluster to open its details panel.
- Click Pause.
- In the Pause cluster? dialog, click Confirm.
The status first changes to Pausing and then to Paused when the operation finishes.
Resume a cluster
If the cluster was suspended by the system, restore the warehouse to an available state before resuming the cluster.
- On the Clusters page, select the cluster that you paused manually.
- Click Resume.
- In the Resume cluster? dialog, click Resume cluster.
The status changes to Starting while VeloDB Cloud provisions the compute resources and mounts the retained cache. When the status changes to Running, the cluster can process requests again.
Configure auto-suspend
Auto-suspend requires core version 4.0.6 or later.
Configurable auto-suspend
You can configure auto-suspend for an eligible cluster when:
- The cluster is Running or was paused manually.
- The warehouse is not Creating.
- You have permission to manage compute resources in the warehouse.
- On the Clusters page, select the cluster to open its details panel.
- In Cluster Details, turn on Auto-suspend.
- In Configure auto-suspend, enter an inactivity period of 1-1,440 minutes for Suspend after.
- Click Enable auto-suspend.
After you enable auto-suspend, VeloDB Cloud pauses the cluster after the configured inactivity period and resumes it automatically when a new workload arrives.
To change the inactivity period, click Edit next to Auto-suspend. In Edit auto-suspend, update the period, and then click Save changes.
To disable the policy, turn off Auto-suspend, then click Confirm in the confirmation dialog.
Auto-suspend during an active trial
During an active trial, Auto-suspend is enabled for all clusters and fixed at 30 minutes. You cannot edit or disable it.
In Cluster Details, click Detail next to Auto-suspend to view the policy. Because Automatic resume is set to Manual, resume the cluster from the console before running queries.
Next steps
- If your core version supports cache warmup, 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.