Lingting Data Recovery Error

Translated
1

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

Original topic: lingting恢复数据报错

| username: Jolyne

[TiDB Usage Environment] Production Environment / Testing / PoC
[TiDB Version]
[Reproduction Path] What operations were performed when the issue occurred
An error occurred while using Lightning to restore data. Is it due to version mismatch?

1687837189918(1)
1687837189918(1)1380×124 34 KB

[Encountered Issue: Issue Phenomenon and Impact]
[Resource Configuration]
[Attachments: Screenshots/Logs/Monitoring]

2
| username: Billmay表妹 | Original post link

Please copy and paste the error message; the image is a bit unclear.

3
| username: Jolyne | Original post link

Verbose debug logs will be written to tidb-lightning.log
tidb lightning encountered error: [Lightning:DB:ErrDBConnect] failed to connect database: commands out of sync. You can’t run this command now

4
| username: Jolyne | Original post link

The image you uploaded is not visible. Please provide the text you need translated.

5
| username: Billmay表妹 | Original post link

I suggest you check whether the versions of TiDB Lightning and TiDB are compatible. You can refer to the Release Notes of TiDB Lightning to see the supported TiDB versions.

6
| username: Billmay表妹 | Original post link

The version of TiDB Lightning should be the same as the cluster.

7
| username: Billmay表妹 | Original post link

If the versions match, you can try the following steps:

  1. Check if the TiDB Lightning configuration file is correct, especially the database connection information.
  2. Verify if TiDB is running properly by using a MySQL client to connect to TiDB and execute some simple SQL statements.
  3. Check the TiDB Lightning log files to see if there are any other error messages. You can enable detailed logging by setting log-level = "debug" in the TiDB Lightning configuration file to better understand the issue.
8
| username: 有猫万事足 | Original post link

What is the content of this file?

9
| username: TiDB_C罗 | Original post link

Check the toml configuration file, and then manually test whether you can connect.

10
| username: Jolyne | Original post link

The default value of tidb_enable_clustered_index is INT_ONLY, which means that only integer primary keys will use clustered indexes by default. If you want to enable clustered indexes for all primary keys, you need to set this parameter to ON.

11
| username: Jolyne | Original post link

Found the error, it’s an issue with haproxy again. Previously configured haproxy incorrectly, didn’t add send-proxy here. Couldn’t log in using proxy port 3390, but now after adding it, 3390 works, but can’t log in through port 4000.

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

If you are using lighting on 55, 56, it should not be able to connect. Non-PROXY protocol connections will be rejected.

13
| username: system | Original post link

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