Skip to content

DM: Add more notes for MariaDB #22087

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dveeden wants to merge 5 commits into
base: master
Choose a base branch
from
+3 −1
Open

DM: Add more notes for MariaDB #22087

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
89cb031
DM: Add note about binlog_legacy_event_pos for MariaDB
dveeden Nov 25, 2025
d3e8bb7
Update dm/dm-compatibility-catalog.md
dveeden Nov 25, 2025
47fe99d
Update migrate-from-mariadb.md
dveeden Nov 25, 2025
4145eb1
Apply suggestion from @dveeden
dveeden Nov 25, 2025
c2b9ecd
Add note about empty gtid_binlog_pos
dveeden Nov 27, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions dm/dm-compatibility-catalog.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,8 @@ DM supports migrating data from different sources to TiDB clusters. Based on the

- For MariaDB **10.5.11 and later**, the DM **precheck fails** due to privilege name changes (for example, `BINLOG MONITOR`, `REPLICATION SLAVE ADMIN`, `REPLICATION MASTER ADMIN`). The error appears as `[code=26005] fail to check synchronization configuration` in the replication privilege, dump privilege, and dump connection number checkers.
- You can **bypass the precheck** by adding `ignore-checking-items: ["all"]` in the DM task. See [DM precheck](/dm/dm-precheck.md) for details.
- For MariaDB 11.4 and later, you must set the [`binlog_legacy_event_pos`](https://mariadb.com/docs/server/ha-and-performance/standard-replication/replication-and-binary-log-system-variables#binlog_legacy_event_pos) variable to `ON`.
Copy link
Contributor

@lance6716 lance6716 Nov 27, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add the related code PR in this PR's description? We can know which versions should be cherry-picked (Sorry I'm busy and still have no time to review that PR)

- Starting DM on a new/fresh MariaDB instance with an empty `gtid_binlog_pos` can cause issues, avoid this by creating at least one transaction. See [GitHub pingcap/tiflow#12423](https://github.com/pingcap/tiflow/issues/12423).

## Target databases

Expand Down
2 changes: 1 addition & 1 deletion migrate-from-mariadb.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ This document describes how to migrate data from a MariaDB server installation t
Choose the right migration strategy:

- The first strategy is to [dump data with Dumpling and restore data with TiDB Lightning](#dump-data-with-dumpling-and-restore-data-with-tidb-lightning). This works for all versions of MariaDB. The drawback of this strategy is that it needs more downtime.
- The second strategy is to [Replicate data with DM](#replicate-data-with-dm) from MariaDB to TiDB with DM. DM does not support all versions of MariaDB. Supported versions are listed on the [DM Compatibility Catalog](/dm/dm-compatibility-catalog.md#compatibility-catalog-of-tidb-data-migration).
- The second strategy is to [Replicate data with DM](#replicate-data-with-dm). DM does not support all versions of MariaDB. Supported versions and required settings are listed on the [DM Compatibility Catalog](/dm/dm-compatibility-catalog.md#compatibility-catalog-of-tidb-data-migration).

Besides these two strategies, there might be other strategies available specifically to your situation. For example:

Expand Down