Skip to content

tikv: clarify description about instance store #23008

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ti-chi-bot merged 6 commits into from
Jun 10, 2026
Merged

tikv: clarify description about instance store #23008

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
ea436a9
Create empty translation PR
hfxsd Jun 5, 2026
82e6a06
Auto-sync: Update English docs from Chinese PR
github-actions[bot] Jun 5, 2026
3090e1b
Update hardware-and-software-requirements.md
hfxsd Jun 5, 2026
df7c5b7
Update hardware-and-software-requirements.md
hfxsd Jun 10, 2026
19e7272
Update hardware-and-software-requirements.md
hfxsd Jun 10, 2026
ba2e70f
Update hardware-and-software-requirements.md
hfxsd Jun 10, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion hardware-and-software-requirements.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -183,7 +183,11 @@ 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.
>
> - 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:

Expand Down
Loading