Does TiKV support expanding capacity by adding new disks and copying original data?

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

Original topic: tikv支持挂新盘拷贝原数据的方式来扩容吗

| username: 扬仔_tidb

【 TiDB Usage Environment】Production Environment
【 TiDB Version】
【Encountered Problem: Problem Phenomenon and Impact】


Currently, the disk on the TiKV node was originally partitioned using MBR, and the content of /etc/fstab is as follows:
/dev/vdd1 /data ext4 defaults 0 0

Now, I don’t want to expand new nodes, but want to mount a new bare disk, then use sync to copy to /data_new, and find a time in the early morning to shut down the cluster, then mount the new disk to the original /data directory.

Is this plan feasible? Is there a faster way to copy other than rsync?

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

Regarding machine maintenance time, I estimate it should be relatively easy.
There shouldn’t be any major issues.

But how did your disk setup pass the installation check?

UUID=c51eb23b-195c-4061-92a9-3fad812cc12f /data1 ext4 defaults,nodelalloc,noatime 0 2

The bold part is what needs to be added to the fstab file before installation. Otherwise, it won’t pass the installation check.

| username: Kongdom | Original post link

:thinking: Isn’t scaling up attractive? Personally, I think scaling up and down is forever the best.

| username: 扬仔_tidb | Original post link

I also don’t know how it passed the check before. This cluster was left to me by the previous expert.

| username: system | Original post link

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