Error in PITR Recovery

Translated
1

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

Original topic: pitr恢复报错

| username: liyuntang

[Test Environment] Testing environment
[TiDB Version] Enterprise Edition 7.1.0
[Reproduction Path] PITR recovery using the br tool
[Encountered Issue: Problem Phenomenon and Impact]
Encountered a “no available connections” error during PITR recovery using the br tool. Specific logs are as follows:

log.file (414.6 KB)

2
| username: Billmay表妹 | Original post link

What does the part showing the error “erro” indicate?

3
| username: Billmay表妹 | Original post link

[Resource Configuration] Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page

Let’s take a look at your configuration~

4
| username: YuJuncen | Original post link

The query log shows:

I1219 14:31:20.340789       9 restore.go:164] [2023/12/19 14:31:20.340 +08:00] [WARN] [client_batch.go:365] ["no available connections"] [target=basic-tikv-0.basic-tikv-peer.e0f36a90-fbc4-48f5-a610-06c7f46e8544.svc:20160]

Perhaps you can check whether the BR pod can connect to basic-tikv-0.basic-tikv-peer.e0f36a90-fbc4-48f5-a610-06c7f46e8544.svc, and whether the corresponding TiKV service has encountered any errors.

5
| username: dba远航 | Original post link

First, ensure that each TiKV has all the recovery files, and then confirm that all database connections are normal.

6
| username: 有猫万事足 | Original post link

When using BR, be sure not to forget to set the rate limit parameter. It’s not difficult for BR to saturate the network, and without setting a rate limit, you can easily encounter strange connection issues.