Dumpling keeps reporting errors when exporting data

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

Original topic: dumpling 导出数据一直报错

| username: TiDBer_RQobNXGv

Dumpling keeps reporting errors when exporting data. The error message is as follows:

| username: zhanggame1 | Original post link

It seems there is an issue with the connection. Have you tried connecting using the MySQL client?

| username: seiang | Original post link

Check if it is a permission issue with the connected account. The permissions required to export data from TiDB/MySQL are:

  • PROCESS: This permission is needed to query cluster information to obtain the PD address, thereby controlling GC through PD.
  • SELECT: Needed when exporting the target table.
  • RELOAD: Needed when using consistency flush. Note that only TiDB supports this permission. If the upstream is RDS or uses managed services, this permission can be ignored.
  • LOCK TABLES: Needed when using consistency lock, and the tables to be exported must have this permission.
  • REPLICATION CLIENT: Needed when exporting metadata to record data snapshot points. This is optional; if you do not need to export metadata, this permission can be ignored.
| username: TiDBer_RQobNXGv | Original post link

There is no problem connecting and querying data using the MySQL client.

| username: TiDBer_RQobNXGv | Original post link

I have always been using the same export statement, only the time condition has changed.

| username: TiDBer_jYQINSnf | Original post link

Post the command and let us take a look.

| username: TiDBer_jYQINSnf | Original post link

Post the command and let us take a look.

| username: TiDBer_RQobNXGv | Original post link

The link you provided appears to be an image. Please provide the text content from the image so I can translate it for you.

| username: changpeng75 | Original post link

Will there be any issues executing the statement “show index from airport.collect” using the MySQL client?

| username: TiDBer_RQobNXGv | Original post link

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

| username: TiDBer_jYQINSnf | Original post link

Looks correct…

| username: 江湖故人 | Original post link

Try downloading the TiDB-community-toolkit from a new node.

| username: 这里介绍不了我 | Original post link

Is the version of the dumpling tool consistent with the cluster version?

| username: 胡杨树旁 | Original post link

Is this machine deployed with HA? Can you log in directly via the command line?

| username: 路在何chu | Original post link

Is it a version mismatch?

| username: forever | Original post link

How about checking the timeout settings? Could it be that there is too much data within the time range, causing the connection to timeout and close?

| username: TiDBer_RQobNXGv | Original post link

The versions are consistent; we have always been using this script.

| username: zhang_2023 | Original post link

The command is correct, that’s strange.

| username: TiDBer_jYQINSnf | Original post link

Use the big guns, Wireshark for packet capture, then start the dumpling command. If it reports an error again, upload the captured packets for us to take a look. Let’s see which IP can’t be connected.

| username: 数据库真NB | Original post link

Connection error, could it be the connection driver or version, or is the account incorrect?