Skip to content
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

updated #20525

Open
wants to merge 2 commits into
base: release-8.1
Choose a base branch
from
Open

updated #20525

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ae40afa
updated
qqqdan Mar 13, 2025
a3a9ab2
Update scale-tidb-cluster.md
qqqdan Mar 13, 2025
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
7 changes: 2 additions & 5 deletions tidb-cloud/scale-tidb-cluster.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,9 +55,6 @@ You can increase or decrease vCPU and RAM of TiDB, TiKV, or TiFlash nodes.

> **Note:**
>
> - Changing vCPU and RAM is only available to the following clusters:
> - Hosted on AWS and created after 2022/12/31.
> - Hosted on Google Cloud and created after 2023/04/26.
> - AWS has a cooldown period of vCPU and RAM changes. If your TiDB cluster is hosted on AWS, after changing the storage or vCPU and RAM of TiKV or TiFlash, you must wait at least six hours before you can change it again.

To change the vCPU and RAM of TiDB, TiKV, or TiFlash nodes, take the following steps:
Expand All @@ -81,8 +78,8 @@ You can increase the storage of TiKV or TiFlash.

> **Warning:**
>
> - For a running cluster, AWS and Google Cloud do not allow in-place storage capacity downgrade.
> - AWS has a cooldown period of storage changes. If your TiDB cluster is hosted on AWS, after changing the storage or vCPU and RAM of TiKV or TiFlash, you must wait at least six hours before you can change it again.
> - For a running cluster, TiDB Cloud do not allow in-place storage capacity downgrade.
> - AWS and Azure has a cooldown period of storage changes. If your TiDB cluster is hosted on AWS or Azure, after changing the storage or vCPU and RAM of TiKV or TiFlash, you must wait at least six hours before you can change it again.

To change the storage of TiKV or TiFlash, take the following steps:

Expand Down