DM Startup Error: invalid connection

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

Original topic: DM启动报错:invalid connection

| username: Kamner

[TiDB Usage Environment] Production Environment
[TiDB Version] 5.4.0
[Reproduction Path] What operations were performed when the issue occurred

[Encountered Issue: Issue Phenomenon and Impact]
DM data synchronization, added a new table, and the startup reported the following error:

| username: Hacker_QGgM2nks | Original post link

Send over the table structure, is there anything special about it?

| username: Kamner | Original post link

Table structure

| username: xiaoqiao | Original post link

Can’t connect?

| username: Kamner | Original post link

The synchronization was normal before. Today, I modified the configuration file and added the table mentioned above. When I started it, an error occurred.

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

This error indicates that it cannot connect to the upstream MySQL.

You can use the MySQL client on the machine where the dm-worker is located to access the upstream. Verify it.

Generally, it is caused by the upstream firewall or user permissions that prevent access.

| username: dba-kit | Original post link

If it was normal before, then show the complete table creation statement with show create table? Looking at the fields, there doesn’t seem to be any special fields; it might be an index issue. TiDB does not support full-text indexing.

| username: Kamner | Original post link

At that time, using the MySQL client to connect and test was normal, but the task couldn’t start.

Now it starts normally.

I checked the load on the source end, and confirmed that the CPU was relatively high during that period, which should be the cause.

| username: Kamner | Original post link

At first, I also suspected it was an issue with the table structure, but later I checked and found no special fields.

| username: RenlySir | Original post link

Does the downstream have this table?

| username: Hacker_PtIIxHC1 | Original post link

  1. Is the upstream MySQL experiencing network isolation or high load, making it unreachable?
  2. Configuration errors (such as domain port, username and password, database name)
| username: system | Original post link

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