Can DM synchronize MySQL 8.0 now?

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

Original topic: dm能同步mysql8.0了吗

| username: tidb狂热爱好者

[TiDB Usage Environment] Production Environment / Testing / PoC
[TiDB Version]
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Issue Phenomenon and Impact]
[Resource Configuration] Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
[Attachment: Screenshot/Logs/Monitoring]
“result”: false,
“msg”: “[code=38032:class=dm-master:scope=internal:level=high], Message: some error occurs in dm-worker: ErrCode:36069 ErrClass:"sync-unit" ErrScope:"upstream" ErrLevel:"high" Message:"get binlog event error: ERROR 1236 (HY000): Could not find first log file name in binary log index file" Workaround:"Please check if the binlog file could be parsed by mysqlbinlog." , Workaround: Please execute query-status to check status.”,
“source”: “mysql-01”,
“worker”: “dm-”
“checkResult”: “pre-check is passed.”

The database has already enabled binlog synchronization. However, there is an error reported within dm. Version 7.6
mysql> show variables like ‘log_bin’;
| Variable_name | Value |
| log_bin | ON |
1 row in set (0.01 sec)

Upstream is Aurora with IO optimization
Downstream is TiDB

| username: Billmay表妹 | Original post link

What are upstream and downstream?

| username: tidb狂热爱好者 | Original post link

I suspect you are here to earn points. Upstream MySQL, downstream TiDB.

| username: zhanggame1 | Original post link

Error content from Baidu, solution:

Close the current binary log file in the master database and create a new file. The name of the new binary log file is the current binary file number plus 1.

mysql> flush logs;
| username: tidb狂热爱好者 | Original post link

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

| username: baozixiaoge | Original post link

Did MySQL generate a binlog? Show master status;

| username: linnana | Original post link

show binary logs;
Are the binlog files still there?

| username: okenJiang | Original post link

Please attach the configuration file. Did you follow the documentation at 从 Amazon Aurora 迁移数据到 TiDB | PingCAP 文档中心?

If so, did you forget to fill in the binlog file and binlog pos in the DM configuration file?

| username: YuchongXU | Original post link

Flush logs;

| username: redgame | Original post link

Hmm, try flushing first, then try again.

| username: zhang_2023 | Original post link

flush logs;

| username: TiDBer_rvITcue9 | Original post link

Flush logs;

| username: TiDBer_5cwU0ltE | Original post link

  • MySQL version = 8.0 (experimental feature)
| username: 考试没答案 | Original post link

The official documentation says it is supported, but it still reports an error when enabled.

| username: GreenGuan | Original post link

The classic MySQL logs have been cleaned up. Set purge binlog to 0, and then use DM for full synchronization.

| username: 江湖故人 | Original post link

Check if the binlog size is normal and if the contents of the binlog index file match. Use mysqlbinlog to analyze the binlog and confirm that there are no SQL statements restricted in TiDB.