From ea436a980efc9c109c277331dfb704fb4f1c1a14 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Fri, 5 Jun 2026 11:29:53 +0800 Subject: [PATCH 1/6] Create empty translation PR From 82e6a0628728d3e705d299309d7f9f892e425dc2 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Fri, 5 Jun 2026 03:31:18 +0000 Subject: [PATCH 2/6] Auto-sync: Update English docs from Chinese PR Synced from: https://github.com/pingcap/docs-cn/pull/21697 Target PR: https://github.com/pingcap/docs/pull/23008 AI Provider: azure Co-authored-by: github-actions[bot] --- hardware-and-software-requirements.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hardware-and-software-requirements.md b/hardware-and-software-requirements.md index 6b82d456507a5..615ac62cc370f 100644 --- a/hardware-and-software-requirements.md +++ b/hardware-and-software-requirements.md @@ -183,7 +183,7 @@ You can deploy and run TiDB on the 64-bit generic hardware server platform in th > - In the production environment, the TiDB and PD instances can be deployed on the same server. If you have a higher requirement for performance and reliability, try to deploy them separately. > - It is strongly recommended to configure TiDB, TiKV, and TiFlash with at least 8 CPU cores each in the production environment. To get better performance, a higher configuration is recommended. > - It is recommended to keep the size of TiKV hard disk within 4 TB if you are using PCIe SSDs or within 1.5 TB if you are using regular SSDs. -> - If you deploy TiKV on a cloud provider, such as AWS, Google Cloud, or Azure, it is recommended to use cloud disks for TiKV nodes. Data on local disks might be lost if the TiKV instance crashes in the cloud environment. +> - If you deploy TiDB clusters on a cloud provider, such as AWS, Google Cloud, or Azure, it is recommended to use cloud disks for TiKV nodes instead of instance store (Instance Store). In the cloud environment, data on instance store might be lost if the host unexpectedly restarts. Before you deploy TiFlash, note the following items: From 3090e1bfd90ab4ab430f6ad94b04041ca9bdb77b Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Fri, 5 Jun 2026 11:33:52 +0800 Subject: [PATCH 3/6] Update hardware-and-software-requirements.md --- hardware-and-software-requirements.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hardware-and-software-requirements.md b/hardware-and-software-requirements.md index 615ac62cc370f..9e117e693130b 100644 --- a/hardware-and-software-requirements.md +++ b/hardware-and-software-requirements.md @@ -183,7 +183,7 @@ You can deploy and run TiDB on the 64-bit generic hardware server platform in th > - In the production environment, the TiDB and PD instances can be deployed on the same server. If you have a higher requirement for performance and reliability, try to deploy them separately. > - It is strongly recommended to configure TiDB, TiKV, and TiFlash with at least 8 CPU cores each in the production environment. To get better performance, a higher configuration is recommended. > - It is recommended to keep the size of TiKV hard disk within 4 TB if you are using PCIe SSDs or within 1.5 TB if you are using regular SSDs. -> - If you deploy TiDB clusters on a cloud provider, such as AWS, Google Cloud, or Azure, it is recommended to use cloud disks for TiKV nodes instead of instance store (Instance Store). In the cloud environment, data on instance store might be lost if the host unexpectedly restarts. +> - If you deploy TiDB clusters on a cloud provider, such as AWS, Google Cloud, or Azure, it is recommended to use cloud disks for TiKV nodes instead of instance store. In the cloud environment, if the node unexpectedly restarts, data on instance store might be lost. Before you deploy TiFlash, note the following items: From df7c5b7a7fe0198acbde4ff49b1d1b9f10d28a08 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Wed, 10 Jun 2026 10:44:16 +0800 Subject: [PATCH 4/6] Update hardware-and-software-requirements.md --- hardware-and-software-requirements.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/hardware-and-software-requirements.md b/hardware-and-software-requirements.md index 9e117e693130b..3877dc99f3d5d 100644 --- a/hardware-and-software-requirements.md +++ b/hardware-and-software-requirements.md @@ -183,7 +183,10 @@ You can deploy and run TiDB on the 64-bit generic hardware server platform in th > - In the production environment, the TiDB and PD instances can be deployed on the same server. If you have a higher requirement for performance and reliability, try to deploy them separately. > - It is strongly recommended to configure TiDB, TiKV, and TiFlash with at least 8 CPU cores each in the production environment. To get better performance, a higher configuration is recommended. > - It is recommended to keep the size of TiKV hard disk within 4 TB if you are using PCIe SSDs or within 1.5 TB if you are using regular SSDs. -> - If you deploy TiDB clusters on a cloud provider, such as AWS, Google Cloud, or Azure, it is recommended to use cloud disks for TiKV nodes instead of instance store. In the cloud environment, if the node unexpectedly restarts, data on instance store might be lost. +> - If you deploy TiDB clusters on a cloud provider, such as AWS, Google Cloud, or Azure, it is recommended to use cloud disks for TiKV nodes instead of instance store. +> - Data durability is relatively low for instance store volumes. The lifecycle of an instance store is tied to the lifecycle of the virtual machine. Data might be lost if the instance is restarted, stopped, migrated, affected by hardware failures, or undergoes maintenance. Most cloud providers explicitly classify instance store as ephemeral storage. For example, according to [AWS documentation](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Storage.html): “The data on an instance store volume persists only during the life of the associated instance; if you stop, hibernate, or terminate an instance, any data on instance store volumes is lost.” +> - Instance store volumes typically do not support snapshots or cross-node or cross-region replication. As a result, data cannot be quickly recovered in the event of corruption or hardware failure. +> - The capacity of an instance store is tied to the instance type and cannot be scaled independently. Before you deploy TiFlash, note the following items: From 19e72725a81979990e804c81233a6637de2d5807 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Wed, 10 Jun 2026 10:51:54 +0800 Subject: [PATCH 5/6] Update hardware-and-software-requirements.md --- hardware-and-software-requirements.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/hardware-and-software-requirements.md b/hardware-and-software-requirements.md index 3877dc99f3d5d..4d29918de49a6 100644 --- a/hardware-and-software-requirements.md +++ b/hardware-and-software-requirements.md @@ -184,9 +184,10 @@ You can deploy and run TiDB on the 64-bit generic hardware server platform in th > - It is strongly recommended to configure TiDB, TiKV, and TiFlash with at least 8 CPU cores each in the production environment. To get better performance, a higher configuration is recommended. > - It is recommended to keep the size of TiKV hard disk within 4 TB if you are using PCIe SSDs or within 1.5 TB if you are using regular SSDs. > - If you deploy TiDB clusters on a cloud provider, such as AWS, Google Cloud, or Azure, it is recommended to use cloud disks for TiKV nodes instead of instance store. -> - Data durability is relatively low for instance store volumes. The lifecycle of an instance store is tied to the lifecycle of the virtual machine. Data might be lost if the instance is restarted, stopped, migrated, affected by hardware failures, or undergoes maintenance. Most cloud providers explicitly classify instance store as ephemeral storage. For example, according to [AWS documentation](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Storage.html): “The data on an instance store volume persists only during the life of the associated instance; if you stop, hibernate, or terminate an instance, any data on instance store volumes is lost.” -> - Instance store volumes typically do not support snapshots or cross-node or cross-region replication. As a result, data cannot be quickly recovered in the event of corruption or hardware failure. -> - The capacity of an instance store is tied to the instance type and cannot be scaled independently. + +> - Data durability is relatively low for instance store volumes. The lifecycle of an instance store is tied to the lifecycle of the virtual machine. Data might be lost if the instance is restarted, stopped, migrated, affected by hardware failures, or undergoes maintenance. Most cloud providers explicitly classify instance store as ephemeral storage. For example, according to [AWS documentation](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Storage.html): “The data on an instance store volume persists only during the life of the associated instance; if you stop, hibernate, or terminate an instance, any data on instance store volumes is lost.” +> - Instance store volumes typically do not support snapshots or cross-node or cross-region replication. As a result, data cannot be quickly recovered in the event of corruption or hardware failure. +> - The capacity of an instance store is tied to the instance type and cannot be scaled independently. Before you deploy TiFlash, note the following items: From ba2e70fb9d7b97df8ec3fc78f273eebb7e6c2f4a Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Wed, 10 Jun 2026 10:52:51 +0800 Subject: [PATCH 6/6] Update hardware-and-software-requirements.md --- hardware-and-software-requirements.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hardware-and-software-requirements.md b/hardware-and-software-requirements.md index 4d29918de49a6..3562506774727 100644 --- a/hardware-and-software-requirements.md +++ b/hardware-and-software-requirements.md @@ -184,7 +184,7 @@ You can deploy and run TiDB on the 64-bit generic hardware server platform in th > - It is strongly recommended to configure TiDB, TiKV, and TiFlash with at least 8 CPU cores each in the production environment. To get better performance, a higher configuration is recommended. > - It is recommended to keep the size of TiKV hard disk within 4 TB if you are using PCIe SSDs or within 1.5 TB if you are using regular SSDs. > - If you deploy TiDB clusters on a cloud provider, such as AWS, Google Cloud, or Azure, it is recommended to use cloud disks for TiKV nodes instead of instance store. - +> > - Data durability is relatively low for instance store volumes. The lifecycle of an instance store is tied to the lifecycle of the virtual machine. Data might be lost if the instance is restarted, stopped, migrated, affected by hardware failures, or undergoes maintenance. Most cloud providers explicitly classify instance store as ephemeral storage. For example, according to [AWS documentation](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Storage.html): “The data on an instance store volume persists only during the life of the associated instance; if you stop, hibernate, or terminate an instance, any data on instance store volumes is lost.” > - Instance store volumes typically do not support snapshots or cross-node or cross-region replication. As a result, data cannot be quickly recovered in the event of corruption or hardware failure. > - The capacity of an instance store is tied to the instance type and cannot be scaled independently.