Restore KV

Translated
1

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

Original topic: 恢复kv

| username: 今天不想写代码

[TiDB Usage Environment] Production Environment
[TiDB Version] 6.2.0
The kv is broken, and now I want to recover it, but there are no spare machines. I want to take down one PD and deploy it together with the DB, then use the PD machine to expand a kv first and then put it back. I wonder if there will be any issues.

2
| username: Daniel-W | Original post link

No problem, just expand directly on the PD node.

3
| username: 今天不想写代码 | Original post link

Can PD nodes coexist with KV nodes? Do they need to be taken offline first?

4
| username: Daniel-W | Original post link

Your environment configuration is a bit low.

5
| username: Daniel-W | Original post link

They can coexist. You can put them on the same machine, but your configuration is a bit low.

6
| username: 今天不想写代码 | Original post link

The minimum configuration, because the user base is not large, around 30,000.

7
| username: 今天不想写代码 | Original post link

Okay, I’ll try it first and then put it back later.

8
| username: 今天不想写代码 | Original post link

timezone Fail no pd found, auto fixing not supported
I would like to ask again about this issue when checking the cluster.

9
| username: zhaokede | Original post link

The solution can be implemented.

10
| username: zhaokede | Original post link

After taking a closer look at the diagram, you can directly use the first TiDB to handle TiKV. The performance and memory resources are somewhat better.

11
| username: 呢莫不爱吃鱼 | Original post link

There should be no problem.

12
| username: Daniel-W | Original post link

Take a look at this, is it the same issue?
tiup check timezone fail [ no pd found ] - TiDB Q&A Community (asktug.com)

13
| username: Daniel-W | Original post link

The version 6.2 should be using tiup 1.10, right? Try running tiup --version to check your tiup version.

14
| username: gary | Original post link
  1. In a production environment, if the PD configuration and TiKV configuration are inconsistent, it may lead to hotspots. It is recommended to apply for a machine with the same configuration to expand the TiKV node.
  2. Mixed deployment also requires resource limitations on the nodes, otherwise resource bottlenecks can easily affect the operation of other nodes.
15
| username: TiDBer_7S8XqKfl | Original post link

Try upgrading the version to see if it resolves the issue.

16
| username: 濱崎悟空 | Original post link

Sure.

17
| username: TiDBer_7S8XqKfl-1158 | Original post link

Try upgrading the version. The current version is relatively low.