Error occurs when using DM to synchronize with PolarDB, always at 98.5% completion

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

Original topic: DM使用polarDB进行同步的时候报错,每次都是到98.5%的时候报错

| username: TiDBer_STGGd1J1

[TiDB Usage Environment] Production Environment
[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/Log/Monitoring]

| username: TiDBer_STGGd1J1 | Original post link

When synchronizing, PolarDB was used, but an error occurred at the end.

| username: WalterWj | Original post link

It looks like the dumpling backup for the po db failed. How about trying a full data backup and restore manually?

| username: 考试没答案 | Original post link

What are the wait_timeout and interactive_timeout settings for PolarDB? How long does it take for you to export data?

| username: tidb菜鸟一只 | Original post link

Are you synchronizing from PolarDB to TiDB?

| username: TiDBer_STGGd1J1 | Original post link

Yes, from PolarDB to TiDB.

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

What version is your PolarDB? Version 8.0?

| username: TiDBer_STGGd1J1 | Original post link

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

| username: TiDBer_STGGd1J1 | Original post link

Data export takes 1 hour.

| username: TiDBer_STGGd1J1 | Original post link

Kernel version
8.0.1.1.40.2

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

Not sure if it’s a compatibility issue between MySQL 8.0 and DM.

| username: tidb菜鸟一只 | Original post link

Does PolarDB support this SQL? SET SESSION TRANSACTION ISOLATION LEVEL REPEATABLE READ;

| username: TiDBer_STGGd1J1 | Original post link

Support, we have changed it to REPEATABLE READ.

| username: TiDBer_STGGd1J1 | Original post link

There were no issues when verifying in the S environment before.

| username: TiDBer_STGGd1J1 | Original post link

Found the reason, mainly because the data volume was relatively large, exceeding MySQL’s pt-kill mechanism limit of 600 seconds, causing the process to be killed. This led to synchronization errors. After consulting the DBA and making adjustments, it is now in the synchronization stage.

| username: yidailatiao | Original post link

From PolarDB to TiDB

| username: system | Original post link

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