[FATAL] [server.rs:698] ["failed to start node: \"[src/server/node.rs:222]: cluster ID mismatch, local 7308238932952239016 != remote 7308318041076050503, you are trying to connect to another cluster, please reconnect to the correct cluster

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

Original topic: [[FATAL] [server.rs:698] "failed to start node: "[src/server/node.rs:222]: cluster ID mismatch, local 7308238932952239016 != remote 7308318041076050503, you are trying to connect to another cluster, please reconnect to th

| username: TiDBer_ZswtPFhU

[TiDB Usage Environment] Production Environment / Testing / Poc
[TiDB Version] tidb-v5.0.1-linux-amd64
[Reproduction Path] What operations were performed when the issue occurred
./bin/tikv-server --pd=“127.0.0.1:2379” --data-dir=/data/tikv --log-file=/data/logs/tikv.log &
Logs:
[WARN] [config.rs:775] [“not on SSD device”] [data_path=/data/tikv/raft]
[ERROR] [server.rs:854] [“failed to init io snooper”] [err_code=KV:Unknown] [err=“"IO snooper is not started due to not compiling with BCC"”]
[FATAL] [server.rs:698] [“failed to start node: "[src/server/node.rs:222]: cluster ID mismatch, local 7308238932952239016 != remote 7308318041076050503, you are trying to connect to another cluster, please reconnect to the correct PD"”]

[Encountered Issue: Issue Phenomenon and Impact]
Due to resource constraints, the superior restarted the system. After restarting the system, the database PD can start normally, but the service cannot start.

[Resource Configuration] Enter TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
[Attachment: Screenshot/Logs/Monitoring]

| username: dba远航 | Original post link

The error message indicates that you might have connected to the wrong cluster name.

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

This is not just a system restart. This log indicates that the cluster_id recorded in the PD connected to by TiKV does not match its own. Has this cluster encountered any issues?

| username: TiDBer_jYQINSnf | Original post link

Check if this PD cluster corresponds to this TiKV cluster.

| username: paulli | Original post link

Did you perform PD recovery?

| username: jiayou64 | Original post link

Have you modified the cluster name?

| username: yiduoyunQ | Original post link

Let’s see if it can be consistently reproduced. Normally, the operations described should not lead to the result mentioned in the title.

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

Didn’t use tiup? This seems to be connecting to the wrong PD node.

| username: Kongdom | Original post link

The prompt is quite clear, the PD is not the PD of this cluster.