Feasibility of Using S3 as Storage for TiKV

This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: tikv使用S3作为存储可行性

| username: TiDB_C罗

[TiDB Usage Environment] Production Environment / Testing / PoC
[TiDB Version]
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Issue Phenomenon and Impact]
In the production environment, there is a data lifecycle, such as retaining data from the past year, while data older than a year is considered cold data with very low access frequency. Is it possible to migrate this cold data to a TiDB cluster based on S3 storage? Has anyone used this before, and are there any points to be aware of?

| username: 有猫万事足 | Original post link

TiKV does not support S3, right?

However, you can use placement rules to schedule infrequently accessed data to cheaper storage corresponding to TiKV. This is currently achievable.

| username: tidb菜鸟一只 | Original post link

Cold data can be backed up to S3 storage and restored when needed.

| username: redgame | Original post link

You can use it manually or create a script.

| username: zhanggame1 | Original post link

Cold data can be stored on mechanical disks, and then the strategy can be adjusted through placement rules.

| username: TiDB_C罗 | Original post link

There will be some low-frequency accesses, such as the historical order function. When you click on more orders from a year ago, the request will be routed to TiDB data, while others will go through MySQL.

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.