Failed to Synchronize Upstream MySQL 5.5 to Downstream TiDB

Translated
1

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

Original topic: 上游MySQL5.5同步到下游TIDB失败报错

| username: 孤君888

[TiDB Usage Environment]
Production Environment
[TiDB Version]
v7.1.2
[Reproduction Path] Operations performed that led to the issue
[Encountered Issue: Problem Phenomenon and Impact]

The system environment is CentOS 7.9. My upstream is MySQL Community Edition 5.5.21 master (it also has a slave), and the downstream is TIDB-v7.1.2. Now, using the DM component to use TiDB as a slave, starting the DM task reports an error. dmctl query-status screenshot below

image
image1380×462 33 KB

DM-Worker node log below:

image
image1380×28 13.2 KB

Supplement: The permissions of the upstream MySQL replication user dmrpl are shown in the figure below:

image
image1104×526 31.9 KB

[Resource Configuration]
[Attachments: Screenshots/Logs/Monitoring]

2
| username: Billmay表妹 | Original post link

MySQL version is too low

System version is too low

3
| username: 小龙虾爱大龙虾 | Original post link

It might be a compatibility issue, TiDB Data Migration 兼容性目录 | PingCAP 文档中心

4
| username: Fly-bird | Original post link

Install version 5.4 of TiDB.

5
| username: 孤君888 | Original post link

Abandon 7.1 and use 5.4? That doesn’t seem appropriate :grinning:

6
| username: 孤君888 | Original post link

I now want to add a 5.6 replica to the upstream 5.5, and then TiDB synchronizing from this 5.6 replica should not report errors, right?

7
| username: Billmay表妹 | Original post link

Practice leads to true knowledge~ Take a look.

8
| username: 像风一样的男子 | Original post link

Judging by the error, it seems to be an issue with the MySQL version. I recommend using MySQL 5.7.

9
| username: oceanzhang | Original post link

Grammatical errors have nothing to do with permissions…

10
| username: oceanzhang | Original post link

I suggest trying to downgrade.

11
| username: xingzhenxiang | Original post link

MySQL upgrade, either add a replica 5.6 and then add a replica 5.7

5.5 → 5.6 → 5.7

12
| username: 路在何chu | Original post link

Set up a 5.7 test database yourself and see if it reports any errors.

13
| username: 路在何chu | Original post link

Create a cascade.

14
| username: 孤君888 | Original post link

I set up a 5.6 replica upstream, and then DM can work by using the 5.6 replica as the data source for synchronization. :grinning:

15
| username: Soysauce520 | Original post link

The official recommendation is MySQL 5.7. MySQL 5.6 may not be sufficient as there are significant differences.

16
| username: oceanzhang | Original post link

It seems that there are fewer issues with 5.7.

17
| username: system | Original post link

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