Scaling TiDB Installed via Binary

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

Original topic: 对使用二进制安装的TIDB进行扩容

| username: TiDBer_dFvnXY5Z

[TiDB Usage Environment] Production/Test Environment/POC
[TiDB Version] TIDBv5.0.1
[Encountered Problem] Failed to scale out TiDB when installing using binary executable files
[Reproduction Path] Installation method: ./bin/pd-server --name=pd1 --data-dir=/data/pd1 --client-urls=“http://172.18.8.230:2379” --peer-urls=“http://172.18.8.230:2380” --advertise-client-urls=“http://172.18.8.230:2379” --advertise-peer-urls=“http://172.18.8.230:2380” --initial-cluster=“pd1=http://172.18.8.230:2380,pd2=http://172.18.8.231:2380,pd3=http://172.18.8.232:2380” -L “info” --log-file=/root/tidb-v5.0.1-linux-amd64/log/pd.log
[Problem Phenomenon and Impact]
Unable to scale out nodes

| username: Meditator | Original post link

Expanding the pd-server cluster requires changing a parameter. By default, it is set to “new” for initializing a new cluster.

| username: TiDBer_dFvnXY5Z | Original post link

Should I add a join before initialization like this, or directly replace the initialization parameters with join?

| username: zzzzzz | Original post link

Replace it, then change it back.

| username: system | Original post link

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