From 1759de8682e75f7a00005bae5e0cc83fd0bf0fa4 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Fri, 8 Nov 2024 10:40:13 +0800 Subject: [PATCH] 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 c96107a48148e..725b226ef8e03 100644 --- a/hardware-and-software-requirements.md +++ b/hardware-and-software-requirements.md @@ -178,7 +178,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 your 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 will be lost if the instance crashes in the cloud environment. +> - If you deploy your 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 instance crashes in the cloud environment. Before you deploy TiFlash, note the following items: