Error Expanding TiDB Using Tiup: cannot find PD in existing cluster

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

Original topic: TiDB使用Tiup扩容时报错 Error: cannot find PD in exist cluster

| username: TiDBer_4UbtzGqZ

[TiDB Usage Environment] Production Environment
[TiDB Version] 6.3.0
[Reproduction Path] Error reported when executing the check command
tiup cluster check ./tidb-scala.yaml

[Encountered Problem: Problem Phenomenon and Impact]
[Resource Configuration]
4c 32GB
[Attachments: Screenshots/Logs/Monitoring]

| username: 像风一样的男子 | Original post link

How is the configuration file yml written?

| username: 普罗米修斯 | Original post link

Is there no PD node in the configuration file?

| username: TiDBer_小阿飞 | Original post link

Check the configuration file?

| username: caiyfc | Original post link

Is the expansion file incorrect?
The topology file for expansion only needs to include information about the components that need to be expanded. Information about existing components and global configurations does not need to be included.

| username: zhanggame1 | Original post link

Compare it with the documentation to see if there is a mistake in the configuration file, and also check the status of the existing cluster to see if it needs to be started.

| username: andone | Original post link

Please post the YAML file for scaling up.

| username: 小龙虾爱大龙虾 | Original post link

It is not recommended to deploy TiDB together with other services in a production environment. I saw your hostname :joy_cat:

| username: Jellybean | Original post link

It is possible that it is mixed with Hadoop machines, or it may have exclusively occupied Hadoop machines (the hostname has not been changed yet).

Regarding the issue raised by the original poster, it is speculated that there might be an error in the configuration file for expansion.

| username: 江湖故人 | Original post link

Do not edit the configuration file yourself. It is best to copy it from the official documentation and modify it to avoid errors. :laughing:

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

Please post the current status of the cluster and the expansion YAML file.

| username: dba远航 | Original post link

Could it be that the PD configuration is incorrect?

| username: Fly-bird | Original post link

Check the configuration file.

| username: ShawnYan | Original post link

Check the tidb-scala.yaml file again, or post it here so everyone can help you take a look.

| username: TiDBer_4UbtzGqZ | Original post link

Write it like this.

| username: Miracle | Original post link

Did you forget to include the cluster name when you checked?

| username: caiyfc | Original post link

I saw what you said, and I went to check the original poster’s command. Indeed, for checking the existing cluster, the command is incorrect :joy:
tiup cluster check
tiup cluster check <cluster-name> scale-out.yml --cluster --user root [-p] [-i /home/root/.ssh/gcp_rsa]

| username: 像风一样的男子 | Original post link

Indeed, the command is missing something. The community experts have sharp eyes.

| username: TiDBer_4UbtzGqZ | Original post link

Great job, indeed it was missing --cluster. The correct command is as follows:
tiup cluster check tidb-test --cluster ./tidb-scale.yaml

| username: system | Original post link

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