Skip to content

[doc][ybm] Correction to scaling limitation #29319

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
+1 −1
Open

[doc][ybm] Correction to scaling limitation #29319

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/content/preview/yugabyte-cloud/cloud-clusters/configure-clusters.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ The **Regions** section on the cluster **Settings > Infrastructure** tab summari
- To avoid data loss, you can only increase disk size per node; once increased, you can't reduce it.
- Currently, you can't change the cluster fault tolerance using the YugabyteDB Aeon UI; you can change it using the [API](../../managed-automation/managed-api/) or [CLI](../../managed-automation/managed-cli/).
- You can't change vCPUs on clusters with fault tolerance of none, you can only increase disk size, or change IOPS (AWS only).
- Changing disk size or IOPS on a cluster with fault tolerance of none results in downtime.
- Changing IOPS on a cluster with fault tolerance of none results in downtime.
- You can't scale Sandbox clusters.
- If another [locking cluster operation](../#locking-operations) is already running, you must wait for it to finish.
- Some scaling operations require a rolling restart or, in the case of clusters with a fault tolerance of none, downtime.
Expand Down