This page describes the cluster management and cluster deletion workflows for CockroachDB Dedicated.
Planning your cluster
Before making any changes to your cluster's nodes or regions, review the requirements and recommendations for CockroachDB Cloud cluster configuration.
View Clusters page
On logging in to the CockroachDB Cloud Console, the Clusters page is displayed. The Clusters page provides a high-level view of your clusters.
For each cluster, the following details display:
- The cluster's Name
- The cluster's Plan Type (Serverless, Dedicated standard, or Dedicated advanced)
- The date and time the cluster was Created
- The cluster's current State
- The cluster's Cloud provider, GCP, AWS, or Azure
- The Version of CockroachDB the cluster is running
The Action button, which is used to:
To view and manage a specific cluster, click the name of the cluster. The Overview page will display.
View cluster overview
The Overview page displays details about the selected CockroachDB Cloud cluster:
The cluster's Configuration shows details about the cluster, its deployment environment, and its nodes, such as the cluster's cloud provider, plan type, regions, and each node's status, compute, and storage.
The Cluster upgrades section shows the cluster's Upgrade window for patch upgrades and the current value for the Delay patch upgrades setting.
The PCI Ready section shows the status of features required for PCI DSS. Requires CockroachDB Dedicated advanced.
The status of security features required for PCI readiness.
From the Overview page, you can connect to your cluster. For more information, see Connect to Your CockroachDB Dedicated Cluster.
Scale your cluster
During limited access, CockroachDB Dedicated clusters on Azure cannot be scaled. Refer to CockroachDB Dedicated on Azure.
Add or remove nodes from a cluster
You can add or remove nodes from your cluster through the Console. See Planning your cluster for cluster requirements and recommendations before proceeding.
You cannot scale a multi-node cluster down to a single-node cluster. If you need to scale down to a single-node cluster, backup your cluster and restore it into a new single-node cluster.
To add or remove nodes from your cluster:
- Navigate to the cluster's Overview page.
Select Actions > Edit cluster.
The Edit cluster page displays.
From the Nodes dropdown, select the number of nodes you want in each region.
In the Summary sidebar, verify the hourly estimated cost for the cluster.
Click Next: Payment.
On the Summary page, verify your new cluster configuration.
Click Update.
Increase storage for a cluster
AWS disks can only be scaled once every six hours.
- Navigate to the cluster's Overview page.
Select Actions > Edit cluster.
The Edit cluster page displays.
Navigate to the Storage dropdown in the Hardware per node section.
Select the new amount of storage per node.
Warning:Storage space cannot be removed due to cloud provider limitations.
In the Summary sidebar, verify the hourly estimated cost for the cluster.
Click Next: Payment.
On the Summary page, verify your new cluster configuration.
Click Update.
Change compute for a cluster
- Navigate to the cluster's Overview page.
Select Actions > Edit cluster.
The Edit cluster page displays.
Navigate to the Compute dropdown in the Hardware per node section.
Select the new amount of vCPUs per node.
Note:When scaling up your cluster, it is generally more effective to increase node size up to 16 vCPUs before adding more nodes. For most production applications, we recommend at least 4 to 8 vCPUs per node.
In the Summary sidebar, verify the hourly estimated cost for the cluster.
Click Next: Payment.
On the Summary page, verify your new cluster configuration.
Click Update.
Set an upgrade window
From your cluster's Overview page, you can view and manage the patch upgrade window for your cluster. During the window, your cluster may experience restarts, degraded performance, and downtime for single-node clusters. To help keep your clusters updated while minimizing disruptions, set a window of time when your cluster is experiencing the lowest traffic. Note that upgrades may not always be completed by the end of the window, and other kinds of cluster maintenance may occur outside the window.
If no upgrade window is set, your cluster will be automatically upgraded as soon as new patch versions are available. Refer to Upgrade Policy.
To set an upgrade window:
- Click the pencil icon next to Cluster upgrades to edit the upgrade window.
- From the Upgrade day dropdown, select the day of the week during which upgrades may be applied.
From the Start of window dropdown, select a start time for your upgrade window in UTC.
The window will last for 6 hours from the start time.
(Optional) If you want to delay automatic upgrades for 60 days, switch Delay patch upgrades to On.
You can enable this setting for development and testing clusters if you want to ensure that they are upgraded before production clusters.
Restore data from a backup
During limited access, managed backups are not available for CockroachDB Dedicated clusters on Azure. Customers can take and restore from their own backups on Azure storage, including encrypted backups. Refer to CockroachDB Dedicated on Azure.
Cockroach Labs runs full backups daily and incremental backups hourly for every CockroachDB Dedicated cluster. Full backups are retained for 30 days and incremental backups for 7 days. See the Use Managed-Service Backups page for ways to restore data from your cluster's automatic backups in the Console.
Additionally, you can back up and restore your CockroachDB Dedicated cluster manually. For detail on taking backups to your cloud storage, see Take and Restore Customer-Owned Backups.
All databases are not backed up at the same time. Each database is backed up every hour based on the time of creation. For larger databases, you might see an hourly CPU spike while the database is being backed up.
Configure PCI ready features (Dedicated advanced)
CockroachDB Dedicated advanced clusters have a PCI ready panel to monitor the status of security features required for PCI readiness. Feature statuses will update from INACTIVE to ACTIVE once you configure them. Learn more about configuring these features:
- CockroachDB Cloud Organization Audit logs
- Customer-Managed Encryption Keys (CMEK)
- Egress Perimeter Controls
- Single Sign-On (SSO) for your CockroachDB Cloud organization and your clusters
- Network security
You can also check the status of these features on the PCI ready page of the CockroachDB Cloud Console.
Delete cluster
Deleting a cluster will delete all cluster data.
You will only be billed for a CockroachDB Dedicated cluster while it is running. You can delete a cluster at any time to stop charges from accumulating.
Proceed with the following steps only if you are sure you want to delete a cluster:
- Navigate to the Overview page for the cluster you want to delete.
- Click the Actions button in the top right corner.
- Select Delete cluster.
- In the confirmation window, enter the name of the cluster.
- Click Delete.