cloud: add the release note for TiDB-X-CLOUD.202510.1 #23147
+172
−6
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,16 +1,30 @@ | ||
| --- | ||
| title: TiDB Cloud Releases | ||
| summary: Learn about TiDB Cloud release notes, kernel versioning, and maintenance notifications. | ||
| --- | ||
|
|
||
| # TiDB Cloud Releases | ||
|
|
||
| [TiDB Cloud](https://www.pingcap.com/tidb/cloud/) is a fully managed Database-as-a-Service (DBaaS) that brings [TiDB](https://docs.pingcap.com/tidb/stable/overview), an open-source Hybrid Transactional and Analytical Processing (HTAP) database, to your cloud. | ||
|
|
||
| TiDB Cloud offers two types of releases: [cloud platform releases](#cloud-platform-release-notes) and [database kernel releases](#database-kernel-release-notes). They follow independent release cycles and are documented separately. | ||
|
|
||
| ## Cloud platform release notes | ||
|
|
||
| Cloud platform releases cover the TiDB Cloud console, APIs, and control plane, including new plan features, UI changes, integrations, and operational improvements across all TiDB Cloud plans. | ||
|
|
||
| - [TiDB Cloud Release Notes](/tidb-cloud/releases/tidb-cloud-release-notes.md) | ||
|
|
||
| ## Database kernel release notes | ||
|
|
||
| The database kernel is the core engine that processes your SQL queries and manages your data. Depending on your TiDB Cloud plan, your resources run on different kernels, each with its own release cadence. | ||
|
|
||
| | Plan | Kernel information and release notes | | ||
| | --- | --- | | ||
| | TiDB Cloud Starter and Essential instances | Run on a customized [TiDB X](/tidb-cloud/tidb-x-architecture.md) engine based on the classic [TiDB v8.5.3](/release-notes/release-8.5.3.md) kernel. | | ||
| | TiDB Cloud Premium instances | Run on the [`TiDB-X-CLOUD.202510.1`](/tidb-cloud/releases/tidb-x-cloud.202510.1.md) version of the [TiDB X](/tidb-cloud/tidb-x-architecture.md) kernel. | | ||
| | TiDB Cloud Dedicated clusters | Run on the classic TiDB kernel, and the kernel version corresponds directly to TiDB Self-Managed versions. Currently, the default TiDB version of newly created TiDB Cloud Dedicated clusters is [v8.5.6](/release-notes/release-8.5.6.md). | | ||
|
|
||
| ## Maintenance notifications | ||
|
|
||
| TiDB Cloud maintenance notifications provide information about scheduled maintenance activities that might affect your TiDB Cloud services. For the list of notifications, see the navigation pane on the left. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,54 @@ | ||
| --- | ||
| title: Kernel Versioning for TiDB Cloud Premium | ||
| summary: Learn about the kernel versioning rules and format for TiDB Cloud Premium. | ||
|
qiancai marked this conversation as resolved.
|
||
| --- | ||
|
|
||
| # Kernel Versioning for TiDB Cloud Premium | ||
|
|
||
| This document describes the versioning rules for the underlying database kernel used by TiDB Cloud Premium. | ||
|
qiancai marked this conversation as resolved.
|
||
|
|
||
| > **Note:** | ||
| > | ||
| > - This document applies only to TiDB Cloud Premium. | ||
| > - TiDB Cloud Starter and Essential instances run on a customized TiDB X engine based on the classic TiDB v8.5.3 kernel. This kernel differs slightly from the TiDB Cloud Premium kernel. | ||
| > - TiDB Cloud Dedicated clusters run on the classic TiDB kernel, and their kernel versions correspond directly to TiDB Self-Managed versions. | ||
|
|
||
|
qiancai marked this conversation as resolved.
|
||
| ## Kernel versioning | ||
|
|
||
| TiDB Cloud Premium kernel versions use the following time-based format: | ||
|
|
||
| ```text | ||
| TiDB-X-CLOUD.YYYYMM.x | ||
| ``` | ||
|
|
||
| For example: | ||
|
|
||
| ```text | ||
| TiDB-X-CLOUD.202510.1 | ||
| ``` | ||
|
|
||
| Where: | ||
|
|
||
| - `YYYYMM` indicates the baseline code branch used to develop the kernel. For example, `202510` means that the baseline branch was created in October 2025. It does not indicate when the kernel version was released. | ||
| - `x` indicates the patch release number for that baseline branch. | ||
|
|
||
| For example, `TiDB-X-CLOUD.202510.1` indicates that the kernel is based on a branch created in October 2025 and is the first patch release built from that branch. | ||
|
|
||
| Because kernel development and release schedules are independent, a kernel version might be released several months after its baseline branch is created. | ||
|
|
||
| Because TiDB Cloud Premium follows its own kernel release cadence, [TiDB Cloud Premium release notes](/tidb-cloud/releases/tidb-x-cloud.202510.1.md) are published separately from [TiDB Self-Managed release notes](https://docs.pingcap.com/releases/tidb-self-managed/). | ||
|
|
||
| ## FAQ | ||
|
|
||
| ### How do I check the kernel version of my TiDB Cloud Premium instance? | ||
|
|
||
| 1. In the [TiDB Cloud console](https://tidbcloud.com/), navigate to the **My TiDB** page, and then click the name of your TiDB Cloud Premium instance to go to its overview page. | ||
| 2. On the overview page, locate the **TiDB version** information in the details pane of your TiDB Cloud Premium instance. | ||
|
|
||
| ### Can I choose the kernel version for my TiDB Cloud Premium instance? | ||
|
|
||
| No. TiDB Cloud manages the entire kernel lifecycle for TiDB Cloud Premium. | ||
|
|
||
| Although the kernel version is displayed for transparency, you cannot select a specific version when creating a TiDB Cloud Premium instance. | ||
|
|
||
| TiDB Cloud automatically provides validated kernel versions for new deployments and performs managed upgrades when appropriate. This helps ensure security, stability, compatibility, and access to the latest features and improvements without requiring manual maintenance. | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,89 @@ | ||
| --- | ||
| title: TiDB-X-CLOUD.202510.1 Release Notes | ||
| summary: Learn about the features for the TiDB-X-CLOUD.202510.1 kernel. | ||
| --- | ||
|
|
||
| # TiDB-X-CLOUD.202510.1 Release Notes | ||
|
|
||
| Release date: April 28, 2026 | ||
|
|
||
| Applicable TiDB Cloud plan: {{{ .premium }}} | ||
|
|
||
| TiDB X kernel version: `TiDB-X-CLOUD.202510.1` | ||
|
|
||
| {{{ .premium }}} is available in public preview starting April 28, 2026, using the `TiDB-X-CLOUD.202510.1` kernel. | ||
|
|
||
| In `TiDB-X-CLOUD.202510.1`: | ||
|
|
||
| - `202510` indicates that the baseline code branch of this kernel version was created in October 2025, which is different from the release date. | ||
| - `1` indicates that it is the first patch release built from the `TiDB-X-CLOUD.202510` baseline branch. | ||
|
|
||
| The `TiDB-X-CLOUD.202510.1` kernel is based on the [TiDB v8.5.0](/releases/release-8.5.0.md) kernel and includes most of the features and improvements introduced in TiDB v8.5.0. | ||
|
|
||
| In addition, compared with the [TiDB v8.5.0](/release-notes/release-8.5.0.md) kernel, the `TiDB-X-CLOUD.202510.1` kernel introduces the following features: | ||
|
|
||
| ## New TiDB X architecture | ||
|
|
||
| * Introduce the TiDB X architecture, which is a cloud-native shared-storage architecture that makes cloud-native object storage the backbone of TiDB. | ||
|
|
||
| This architecture enables elastic scalability, predictable performance, and optimized total cost of ownership (TCO) for AI-era workloads. | ||
|
|
||
| TiDB X represents a fundamental evolution from the shared-nothing architecture of [classic TiDB](/tidb-architecture.md) to a cloud-native shared-storage architecture. By transitioning from a shared-nothing to a shared-storage architecture, TiDB X addresses the physical limitations of coupled nodes to achieve the following technical objectives: | ||
|
|
||
| - **Accelerated scaling**: Improving scaling performance by up to 10x by eliminating the need for physical data migration. | ||
| - **Task isolation**: Ensuring zero interference between background maintenance tasks (such as compaction) and online transactional traffic. | ||
| - **Resource elasticity**: Implementing a true "pay-as-you-go" model where compute resources scale independently of storage volume. | ||
|
|
||
| For more information, see [TiDB X Architecture](/tidb-cloud/tidb-x-architecture.md). | ||
|
|
||
| ## Performance features | ||
|
|
||
| * Support redistributing data of a specific table (experimental) [#63260](https://github.com/pingcap/tidb/issues/63260) @[bufferflies](https://github.com/bufferflies) | ||
|
|
||
| PD automatically schedules data to be distributed as evenly as possible across all TiKV nodes in a cluster. However, this automatic scheduling focuses on the cluster as a whole. In some cases, even if the cluster-wide data distribution is balanced, the data of a specific table might still be unevenly distributed across TiKV nodes. | ||
|
|
||
| Now you can use the [`SHOW TABLE DISTRIBUTION`](https://docs.pingcap.com/tidb/v8.5/sql-statement-show-table-distribution/) statement to check how the data of a specific table is distributed across all TiKV nodes. If the data distribution is unbalanced, you can use the [`DISTRIBUTE TABLE`](https://docs.pingcap.com/tidb/v8.5/sql-statement-distribute-table) statement to redistribute the table's data (experimental) to improve load balancing. | ||
|
|
||
| Note that redistributing the data of a specific table is a one-time task with a timeout limit. If the distribution task is not completed before the timeout, it will automatically exit. | ||
|
|
||
| For more information, see [documentation](https://docs.pingcap.com/tidb/v8.5/sql-statement-distribute-table). | ||
|
|
||
| * Support `ANALYZE` embedded in DDL statements [#57948](https://github.com/pingcap/tidb/issues/57948) @[terry1purcell](https://github.com/terry1purcell) @[AilinKid](https://github.com/AilinKid) | ||
|
|
||
| This feature applies to the following types of DDL statements: | ||
|
|
||
| - DDL statements that create new indexes: [`ADD INDEX`](/sql-statements/sql-statement-add-index.md) | ||
| - DDL statements that reorganize existing indexes: [`MODIFY COLUMN`](/sql-statements/sql-statement-modify-column.md) and [`CHANGE COLUMN`](/sql-statements/sql-statement-change-column.md) | ||
|
|
||
| When you enable this feature, TiDB automatically runs an `ANALYZE` (statistics collection) operation before the new or reorganized index becomes visible to users. This prevents inaccurate optimizer estimates and potential plan changes caused by temporarily unavailable statistics after index creation or reorganization. | ||
|
|
||
| For more information, see [documentation](https://docs.pingcap.com/tidb/v8.5/ddl_embedded_analyze). | ||
|
|
||
| ## Observability features | ||
|
|
||
| * Add storage engine identifiers to statement summary tables and slow query logs [#61736](https://github.com/pingcap/tidb/issues/61736) @[henrybw](https://github.com/henrybw) | ||
|
|
||
| When both TiKV and TiFlash are deployed in a cluster, users often need to filter SQL statements by storage engine during database diagnostics and performance optimization. For example, if TiFlash is under high load, users might need to identify SQL statements running on TiFlash to locate potential causes. To meet this need, TiDB now adds storage engine identifier fields to statement summary tables and slow query logs. | ||
|
|
||
| New fields in [statement summary tables](/statement-summary-tables.md): | ||
|
|
||
| * `STORAGE_KV`: `1` indicates that the SQL statement accesses TiKV. | ||
| * `STORAGE_MPP`: `1` indicates that the SQL statement accesses TiFlash. | ||
|
|
||
| New fields in [slow query logs](/identify-slow-queries.md): | ||
|
|
||
| * `Storage_from_kv`: `true` indicates that the SQL statement accesses TiKV. | ||
| * `Storage_from_mpp`: `true` indicates that the SQL statement accesses TiFlash. | ||
|
|
||
| This feature simplifies workflows in certain diagnostics and performance optimization scenarios and improves issue identification efficiency. | ||
|
|
||
| For more information, see [Statement Summary Tables](/statement-summary-tables.md) and [Identify Slow Queries](/identify-slow-queries.md). | ||
|
|
||
| ## Limitations | ||
|
|
||
| Because of the architectural differences between TiDB X and classic TiDB, the TiDB X kernel does not support the following storage features of the classic TiDB kernel: | ||
|
|
||
|
Collaborator
There was a problem hiding this comment. Because of the architectural differences between TiDB X and classic TiDB, the
Collaborator
There was a problem hiding this comment. I think it doesn't need to specify the tidb kernel version v8.5.0 for tikv. |
||
| - [TiKV MVCC In-Memory Engine (IME)](/tikv-in-memory-engine.md) | ||
| - [Follower Read](/follower-read.md) | ||
|
|
||
| To learn more about the limitations, see [Limited SQL features on TiDB X Instances](/tidb-cloud/limited-sql-features-tidb-x.md). | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.