Skip to content

update CM part for Azure public review #20841

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 2 commits into
base: support-azure
Choose a base branch
from
+4 −4
Open

update CM part for Azure public review #20841

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c399024
changes
qqqdan Apr 23, 2025
ce4926c
minor wording updates
qiancai Apr 25, 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
6 changes: 3 additions & 3 deletions tidb-cloud/scale-tidb-cluster.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ You can increase or decrease vCPU and RAM of TiDB, TiKV, or TiFlash nodes.
> - 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.
> - AWS has a cooldown period of vCPU and RAM changes. If your TiDB cluster is hosted on AWS, after changing the 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 +81,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, AWS, Azure, and Google Cloud do not allow in-place storage capacity downgrade.
> - AWS and Azure have 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
2 changes: 1 addition & 1 deletion tidb-cloud/upgrade-tidb-cluster.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ For the TiDB version that is too low, TiDB Cloud will regularly upgrade it unifo

To submit an upgrade request, perform the steps in [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) to contact our support team. Note to provide the following information in the **Description** box:

- Cloud Provider: Google Cloud or AWS
- Cloud Provider: AWS, Azure, or Google Cloud
- Cluster Name: xxx

TiDB Cloud technical support will confirm with you the time period for the upgrade. After you have confirmed the upgrade time, TiDB Cloud technical support will do the upgrade in the confirmed time period.