From d219ce36d573f32df1b647ef8f1b99b446ad7af8 Mon Sep 17 00:00:00 2001 From: doc-claw-bot Date: Tue, 27 Oct 2026 06:41:43 +0000 Subject: [PATCH 1/6] cloud: add cloud release notes for release-20261027 --- tidb-cloud/releases/tidb-cloud-release-notes.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/tidb-cloud/releases/tidb-cloud-release-notes.md b/tidb-cloud/releases/tidb-cloud-release-notes.md index 77477be50b4f3..065f00e9c52c5 100644 --- a/tidb-cloud/releases/tidb-cloud-release-notes.md +++ b/tidb-cloud/releases/tidb-cloud-release-notes.md @@ -8,6 +8,23 @@ aliases: ['/tidbcloud/supported-tidb-versions','/tidbcloud/release-notes','/ai/v This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-cloud/) in 2026. +## October 27, 2026 + +**General changes** + +- **TiDB Cloud Essential** + + - TiDB Cloud Essential now supports **Regional High Availability** in `Tokyo (ap-northeast-1)`, with support for additional regions rolling out gradually. + + When creating a new TiDB Cloud Essential instance in a supported region, you can choose between **Zonal** (single Availability Zone) and **Regional** (multiple Availability Zones) high availability. + + Regional high availability provides enhanced resilience against Availability Zone failures and costs more than Zonal high availability. + + - For TiDB Cloud Essential instances with Regional High Availability created before October 26, 2026, the new pricing will take effect in January 2027. + - For TiDB Cloud Essential instances created on or after October 26, 2026, the new pricing applies immediately upon creation. + + For more information, see [TiDB Cloud Essential Pricing Details](https://www.pingcap.com/tidb-cloud-essential-pricing-details/). + ## October 20, 2026 **General changes** From b297cbfea555b5ef6bd736ce199fb82a8cb40c90 Mon Sep 17 00:00:00 2001 From: qiancai Date: Tue, 27 Oct 2026 17:37:03 +0800 Subject: [PATCH 2/6] Update tidb-cloud-release-notes.md --- tidb-cloud/releases/tidb-cloud-release-notes.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/tidb-cloud/releases/tidb-cloud-release-notes.md b/tidb-cloud/releases/tidb-cloud-release-notes.md index 065f00e9c52c5..234a31f2fc3b8 100644 --- a/tidb-cloud/releases/tidb-cloud-release-notes.md +++ b/tidb-cloud/releases/tidb-cloud-release-notes.md @@ -18,17 +18,23 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c When creating a new TiDB Cloud Essential instance in a supported region, you can choose between **Zonal** (single Availability Zone) and **Regional** (multiple Availability Zones) high availability. - Regional high availability provides enhanced resilience against Availability Zone failures and costs more than Zonal high availability. + Regional High Availability provides enhanced resilience against Availability Zone failures. For TiDB Cloud Essential, the new regional RCU price is now higher than the previous price, while zonal RCU pricing remains unchanged. The new Regional price takes effect as follows: - For TiDB Cloud Essential instances with Regional High Availability created before October 26, 2026, the new pricing will take effect in January 2027. - For TiDB Cloud Essential instances created on or after October 26, 2026, the new pricing applies immediately upon creation. - For more information, see [TiDB Cloud Essential Pricing Details](https://www.pingcap.com/tidb-cloud-essential-pricing-details/). + For RCU pricing details, see [TiDB Cloud Essential Pricing Details](https://www.pingcap.com/tidb-cloud-essential-pricing-details/). ## October 20, 2026 **General changes** +- **TiDB Cloud Starter** + + - Chat2Query is no longer supported in [SQL Editor](https://docs.pingcap.com/tidbcloud/explore-data-with-sql-editor/?plan=starter&compatibility=mysql) and [Data Service](https://docs.pingcap.com/tidbcloud/data-service-overview/?plan=starter&compatibility=mysql). + + Starting from October 20, 2026, TiDB Cloud no longer supports Chat2Query in SQL Editor or Data Service. This change only affects Chat2Query and the Chat2Query API. All other features in SQL Editor and Data Service remain available. + - **TiDB Cloud Essential and Premium** - TiDB Cloud Essential and Premium support [New Relic](https://newrelic.com/) metrics integration (public preview). From 9a6be4dd092b35a5e51478bbc32eef5b98b0c514 Mon Sep 17 00:00:00 2001 From: qiancai Date: Tue, 27 Oct 2026 17:37:09 +0800 Subject: [PATCH 3/6] Update serverless-high-availability.md --- tidb-cloud/serverless-high-availability.md | 25 +--------------------- 1 file changed, 1 insertion(+), 24 deletions(-) diff --git a/tidb-cloud/serverless-high-availability.md b/tidb-cloud/serverless-high-availability.md index 2df2811cb8bd7..b0a4040382973 100644 --- a/tidb-cloud/serverless-high-availability.md +++ b/tidb-cloud/serverless-high-availability.md @@ -18,24 +18,11 @@ TiDB ensures high availability and data durability using the Raft consensus algo TiDB Cloud extends these capabilities with zonal high availability and regional high availability to meet different operational requirements. - - -> **Note:** -> -> - For {{{ .starter }}} and Essential instances, only zonal high availability is enabled, and it is not configurable. -> - For {{{ .premium }}} instances, only regional high availability is enabled and is not configurable. - - - - - > **Note:** > > - For {{{ .starter }}} instances, only zonal high availability is enabled, and it is not configurable. > - For {{{ .premium }}} instances, only regional high availability is enabled and is not configurable. -> - For {{{ .essential }}} instances hosted in the AWS Tokyo (ap-northeast-1) region, regional high availability is enabled by default. You can change it to zonal high availability as needed during {{{ .essential }}} instance creation. For {{{ .essential }}} instances hosted in other regions, only zonal high availability is enabled, and it is not configurable. - - +> - For {{{ .essential }}} instances hosted in the AWS `Tokyo (ap-northeast-1)` region, regional high availability is enabled by default. You can change it to zonal high availability as needed during {{{ .essential }}} instance creation. For {{{ .essential }}} instances hosted in other regions, only zonal high availability is enabled, and it is not configurable. - **Zonal high availability**: This option places all nodes within a single availability zone, reducing network latency. It ensures high availability without requiring application-level redundancy across zones, making it suitable for applications that prioritize low latency within a single zone. For more information, see [Zonal high availability architecture](#zonal-high-availability-architecture). @@ -99,18 +86,8 @@ The gateway and computing layers are stateless, so failover involves restarting ## Regional high availability architecture - - When you create a {{{ .essential }}} or {{{ .premium }}} instance with regional high availability, critical OLTP (Online Transactional Processing) workload components, such as PD and TiKV, are deployed across multiple availability zones to ensure redundant replication and maximizing availability. During normal operations, components like Gateway, TiDB, and TiFlash compute/write nodes are hosted in the primary availability zone. These components in data plane offer infrastructure redundancy through virtual machine pools, which minimizes failover time and network latency due to colocation. - - - - -When you create a {{{ .premium }}} instance with regional high availability, critical OLTP (Online Transactional Processing) workload components, such as PD and TiKV, are deployed across multiple availability zones to ensure redundant replication and maximize availability. During normal operations, components like Gateway, TiDB, and TiFlash compute/write nodes are hosted in the primary availability zone. These components in the data plane offer infrastructure redundancy through virtual machine pools, which minimizes failover time and network latency due to colocation. - - - > **Note:** > > Regional high availability is currently in public preview. From f4f1b1493485f01aa03ea1b3f26f03fc9af0fa70 Mon Sep 17 00:00:00 2001 From: qiancai Date: Tue, 27 Oct 2026 17:38:24 +0800 Subject: [PATCH 4/6] Update tidb-cloud-release-notes.md --- tidb-cloud/releases/tidb-cloud-release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tidb-cloud/releases/tidb-cloud-release-notes.md b/tidb-cloud/releases/tidb-cloud-release-notes.md index 234a31f2fc3b8..3655d963f0009 100644 --- a/tidb-cloud/releases/tidb-cloud-release-notes.md +++ b/tidb-cloud/releases/tidb-cloud-release-notes.md @@ -14,7 +14,7 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c - **TiDB Cloud Essential** - - TiDB Cloud Essential now supports **Regional High Availability** in `Tokyo (ap-northeast-1)`, with support for additional regions rolling out gradually. + - TiDB Cloud Essential now supports **Regional High Availability** (public preview) in `Tokyo (ap-northeast-1)`, with support for additional regions rolling out gradually. When creating a new TiDB Cloud Essential instance in a supported region, you can choose between **Zonal** (single Availability Zone) and **Regional** (multiple Availability Zones) high availability. From 00c8468676122328bb3ed165fbd37c79cad29959 Mon Sep 17 00:00:00 2001 From: Lilian Lee Date: Tue, 27 Oct 2026 17:49:20 +0800 Subject: [PATCH 5/6] Apply suggestions from code review --- tidb-cloud/releases/tidb-cloud-release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tidb-cloud/releases/tidb-cloud-release-notes.md b/tidb-cloud/releases/tidb-cloud-release-notes.md index 3655d963f0009..0ebbcfbdb4755 100644 --- a/tidb-cloud/releases/tidb-cloud-release-notes.md +++ b/tidb-cloud/releases/tidb-cloud-release-notes.md @@ -33,7 +33,7 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c - Chat2Query is no longer supported in [SQL Editor](https://docs.pingcap.com/tidbcloud/explore-data-with-sql-editor/?plan=starter&compatibility=mysql) and [Data Service](https://docs.pingcap.com/tidbcloud/data-service-overview/?plan=starter&compatibility=mysql). - Starting from October 20, 2026, TiDB Cloud no longer supports Chat2Query in SQL Editor or Data Service. This change only affects Chat2Query and the Chat2Query API. All other features in SQL Editor and Data Service remain available. + Starting from October 20, 2026, TiDB Cloud no longer supports Chat2Query in SQL Editor and Data Service. This change only affects Chat2Query and the Chat2Query API. All other features in SQL Editor and Data Service remain available. - **TiDB Cloud Essential and Premium** From 3a8c20777d066f0a5628d38ee0974ac5a399f526 Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Tue, 27 Oct 2026 17:55:14 +0800 Subject: [PATCH 6/6] Update tidb-cloud/serverless-high-availability.md Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> --- tidb-cloud/serverless-high-availability.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tidb-cloud/serverless-high-availability.md b/tidb-cloud/serverless-high-availability.md index b0a4040382973..2011b43c0cbf9 100644 --- a/tidb-cloud/serverless-high-availability.md +++ b/tidb-cloud/serverless-high-availability.md @@ -86,7 +86,7 @@ The gateway and computing layers are stateless, so failover involves restarting ## Regional high availability architecture -When you create a {{{ .essential }}} or {{{ .premium }}} instance with regional high availability, critical OLTP (Online Transactional Processing) workload components, such as PD and TiKV, are deployed across multiple availability zones to ensure redundant replication and maximizing availability. During normal operations, components like Gateway, TiDB, and TiFlash compute/write nodes are hosted in the primary availability zone. These components in data plane offer infrastructure redundancy through virtual machine pools, which minimizes failover time and network latency due to colocation. +When you create a {{{ .essential }}} or {{{ .premium }}} instance with regional high availability, critical OLTP (Online Transactional Processing) workload components, such as PD and TiKV, are deployed across multiple availability zones to ensure redundant replication and maximize availability. During normal operations, components like Gateway, TiDB, and TiFlash compute/write nodes are hosted in the primary availability zone. These components in data plane offer infrastructure redundancy through virtual machine pools, which minimizes failover time and network latency due to colocation. > **Note:** >