Manage clusters
YugabyteDB Managed provides the following tools to manage clusters:
| Feature | Description |
|---|---|
| Scaling | To ensure the cluster configuration matches its performance requirements, scale the cluster vertically or horizontally as your requirements change. |
| Read replicas | Add read replicas to lower read latencies in regions that are distant from your primary cluster. |
| Backups | Configure a regular backup schedule, run manual backups, and review previous backups. |
| Maintenance windows | Yugabyte only performs cluster maintenance, including database upgrades, during a weekly maintenance window that you configure. |
| PostgreSQL extensions | Extend the functionality of your cluster using PostgreSQL extensions. |
Pause, resume, and delete clusters
To reduce costs on unused clusters, you can pause or delete them.
Access Pause/Resume Cluster and Terminate Cluster via the cluster Actions menu, or click the three dots icon for the cluster on the Clusters page.
Deleting a cluster deletes all of its data, including backups.
Paused clusters are not billed for instance vCPU capacity. Disk and backup storage are charged at the standard rate (refer to Cluster costs). You can't change the configuration, or read and write data to a paused cluster. Alerts and backups are also stopped. Existing backups remain until they expire. You can't pause a Sandbox cluster. Yugabyte notifies you when a cluster is paused for 30 days.
Note that if another locking operation is in progress, you can't pause or delete a cluster until the other operation completes.
Locking operations
Cluster infrastructure operations lock the cluster while they are in progress, and only one can happen at the same time. Some operations also require a restart.
| Locking Operation | Subtask | Restart |
|---|---|---|
| Backup and restore | ||
| Pause and resume | ||
| Cluster Edit | Add or remove nodes | |
| Cluster Edit | Change vCPUs, increase disk size, or change IOPS | Yes |
| Read replica edit | Create or delete; add or remove nodes | |
| Read replica edit | Increase disk size, change IOPS | Yes |
| Configure metrics export | ||
| Scheduled maintenance | Database upgrades, certificate rotations, and cluster maintenance (A backup is run automatically before a database upgrade) |
Yes |
Keep in mind the following:
-
For clusters with Node, Availability Zone, or Region fault tolerance, and read replicas with a replication factor greater than 1, restarts are rolling. Your database will continue to function normally during infrastructure operations, but these operations can temporarily degrade application performance.
-
For clusters with fault tolerance of none, and read replicas with a replication factor of 1, restarts will result in downtime for the cluster or read replica.
-
You should schedule infrastructure operations during periods of low traffic.
-
On AWS, any disk modification (size or IOPS) blocks further disk modifications for six hours (this includes a scaling operation that increases the number of vCPUs, as this also increases disk size).
-
Make sure that you schedule maintenance and backups so that they do not conflict.
