Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
Co-authored-by: qqqdan <[email protected]>
  • Loading branch information
hfxsd and qqqdan authored Dec 20, 2024
1 parent 53f2ef6 commit 6dee30f
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion tidb-cloud/tidb-node-group-overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,6 +54,6 @@ Currently, the TiDB Node Group feature is in private beta and free of charge. Th

## SLA impact

According to TiDB Cloud [Service Level Agreement (SLA)](https://www.pingcap.com/legal/service-level-agreement-for-tidb-cloud-services/), the Monthly Uptime Percentage of TiDB Cloud Dedicated clusters with multiple TiDB nodes deployment can reach up to 99.99%. However, after introducing the TiDB Node Group feature, TiDB Cloud can not provide high availability across TiDB node groups. If you create multiple TiDB node groups with only one TiDB node in each group, you will lose the high availability for the groups and your cluster's monthly uptime percentage will downgrade to a single TiDB node deployment model.
According to TiDB Cloud [Service Level Agreement (SLA)](https://www.pingcap.com/legal/service-level-agreement-for-tidb-cloud-services/), the Monthly Uptime Percentage of TiDB Cloud Dedicated clusters with multiple TiDB nodes deployment can reach up to 99.99%. However, after introducing the TiDB Node Group feature, TiDB Cloud can not provide TiDB node level high availability across TiDB node groups. If you create multiple TiDB node groups with only one TiDB node in each group, you will lose the high availability for the groups and your cluster's monthly uptime percentage will downgrade to the single TiDB node deployment model.

For high availability, it is recommended that you configure at least two TiDB nodes for each TiDB node group.

0 comments on commit 6dee30f

Please sign in to comment.