View and Manage Clusters
View clusters and inspect their resources, configuration, and lifecycle details.
Open the cluster list
- 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.
- Click Physical Clusters.
View clusters in Table view
Click Table to view the cluster list. The table always displays Cluster Name / ID, Status, Compute, Cache, and Actions.
Use the controls above the table to:
- Enter a cluster name or ID in Search by cluster name / ID.
- Select a value in All status to filter clusters by status.
- Open Customize columns to show or hide CPU utilization, memory utilization, disk cache utilization, disk cache hit rate, and creation time.
- Click Refresh to fetch the latest cluster state.
You can perform some cluster actions directly from the row. Click a cluster row to open its details page for additional actions.
Inspect a cluster in Card view
Click Card, then select a cluster in the list. The details panel contains Resource Overview and Cluster Details.
Resource Overview
Resource Overview shows the cluster's current compute, memory, and cache capacity. Utilization and cache hit rate values are averages over the last five minutes:
- CPU Utilization and total vCPU.
- Memory Utilization and total RAM.
- Disk Cache Utilization and total cache capacity.
- Disk Cache Hit Rate.
Click a metric to open its chart on the Metrics page.
Cluster Details
Cluster Details displays the cluster's scaling configuration and lifecycle information.
Depending on the warehouse configuration, the panel displays the following fields:
| Field | Description |
|---|---|
| Auto-suspend | Whether automatic suspension is enabled. When available, use the switch or Edit to change the setting. |
| Scaling Mode | The active scaling strategy: Manual Scaling, Auto Scaling, or Time-based Scaling. |
| Created By | The user who created the cluster. |
| Zone | The availability zone where the cluster runs. |
| Created At | The time when the cluster was created. The label includes the time zone used for the displayed value. |
| Started At | The start time of the cluster's current running period. Unavailable while the cluster is creating or paused. |
| Running Time | The elapsed time since Started At. Unavailable while the cluster is creating or paused. |
For information about charges and billing statements, see Billing.
Rename a cluster
You need permission to manage compute resources in the warehouse.
The cluster must be Running. You cannot rename a physical cluster while it is mounted as the active or standby cluster of a virtual cluster.
Warning:
After renaming a cluster, update application settings and SQL statements that explicitly reference the old name. Requests that still reference the old name can fail.
- In Card view, select the cluster.
- Next to the cluster name, click the Edit icon.
- Enter a name that starts with a letter and contains up to 32 characters. Use only letters, digits, or underscores. Do not use consecutive underscores. The name must be unique across physical and virtual clusters in the warehouse. Names are compared case-insensitively.
- Press Enter or click the Confirm icon.
- In the Rename the cluster? dialog, review the impact, then click Confirm.
- Verify that the new name appears in the cluster list and details panel.
Use cluster actions
The available actions depend on your permissions, the warehouse status, the cluster status, the billing method, and whether the cluster belongs to a virtual cluster.
In the upper-right corner, click .... The menu contains Restart, View metrics, and Delete.
| Action | Result |
|---|---|
| Scaling | Opens the available on-demand scaling settings. See Scale a cluster. |
| Pause or Resume | Pauses or resumes eligible resources. See Pause and resume a cluster. |
| Refresh | Refreshes the cluster details and resource metrics. |
| Restart | Restarts the cluster's compute resources. See Restart a cluster. |
| View metrics | Opens the cluster on the Metrics page. |
| Delete | Deletes an eligible cluster. See Delete a cluster. |
Next steps
- Pause and resume a cluster to control idle compute charges.
- Scale a cluster when workload demand changes.
- Manage warmup jobs to prepare cached data before production traffic.