Stopping the TiDB Cluster Affected the TiKV Cluster

Translated
1

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

Original topic: 停了tidb集群 影响了tikv集群

| username: TiDBer_30hewbUu

[TiDB Usage Environment] Production Environment
[TiDB Version] 5.0.1
[Reproduction Path]
[Encountered Problem: Problem Phenomenon and Impact] Stopped the TiDB cluster, and connecting to the TiKV cluster resulted in a timeout
[Resource Configuration]
[Attachment: Screenshot/Log/Monitoring]

1: Declaration: Deployed a set of TiDB clusters on three servers including: tidb3 PD3 tikv3
One TiKV cluster: PD3, TIKV*3. Differentiated the two clusters by ports

image
image1380×436 83.1 KB

tidb:

image
image1380×492 116 KB

This tidb has already stopped the tidb node. It did not affect the tikv cluster. Now, after stopping everything, the backend service tikv connection also timed out. It seems that this cluster is mixed up with tiup. What exactly is the reason?

2
| username: xfworld | Original post link

Are your two clusters using a single set of resources or two separate sets of resources?

How did you set it up? It looks quite messy…

3
| username: TiDBer_30hewbUu | Original post link

The backend configuration was incorrect. This issue has been resolved.

4
| username: system | Original post link

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