Consultation on DM Synchronization Issues

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

Original topic: dm同步问题咨询

| username: Hacker007

As shown in the figure, the table creation statement (some fields omitted):


MySQL insert statement:

DM synchronization exception:

TiDB data:

Logically, executing the replace into statement in MySQL would generate two statements: delete and insert. Why does DM indicate a primary key conflict? The main issue is that this exception can be resolved using the resume-task statement, whereas normal primary key conflicts cannot be resolved this way.

| username: 大飞哥online | Original post link

It looks like this has only been converted to insert into, not delete + insert.

| username: Fly-bird | Original post link

delete + insert

| username: Hacker007 | Original post link

Does anyone know the principle?

| username: 大飞哥online | Original post link

DM for version 5.2?

| username: andone | Original post link

delete + insert

| username: Jellybean | Original post link

The reason for the error is indicated here; it has been converted to insert. However, this conversion is not idempotent. You can try using a higher version of DM.

| username: swino | Original post link

Try a higher version.

| username: Hacker007 | Original post link

TiDB is 5.2, DM is v2.0.6. At that time, TiDB and DM did not have unified versions yet.

| username: Hacker007 | Original post link

It is not a good time to upgrade the version now due to risks and cost constraints.

| username: system | Original post link

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