Skip to content

DM: Update MariaDB config hints #22789

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 2 commits into
base: master
Choose a base branch
from
+11 −1
Open

DM: Update MariaDB config hints #22789

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
adde0ea
DM: Update MariaDB config hints
dveeden Apr 21, 2026
1b731e2
Update migrate-from-mariadb.md
dveeden Apr 21, 2026
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
10 changes: 10 additions & 0 deletions dm/dm-precheck.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -139,6 +139,16 @@ For the incremental data migration mode (`task-mode: incremental`), in addition
- Check whether `binlog_transaction_compression=OFF` is configured (DM does not support transaction compression).
- If `binlog_do_db` or `binlog_ignore_db` is configured, check whether the database tables to be migrated meet the conditions of `binlog_do_db` and `binlog_ignore_db`.

* (Mandatory) MariaDB binlog configuration

- Check whether binlog is enabled (required by DM).
- Check whether `binlog_legacy_event_pos` is set to `ON`.
- Check whether `binlog_format=ROW` is configured (DM only supports the migration of binlog in the ROW format).
- Check whether `binlog_row_image=FULL` is configured (DM only supports `binlog_row_image=FULL`).
- If `binlog_do_db` or `binlog_ignore_db` is configured, check whether the database tables to be migrated meet the conditions of `binlog_do_db` and `binlog_ignore_db`.
- Check whether `binlog_annotate_row_events` is set to `OFF`.
- Check whether `log_bin_compress` is set to `OFF`.

* (Mandatory) Check if the upstream database is in an [Online-DDL](/dm/feature-online-ddl.md) process (in which the `ghost` table is created but the `rename` phase is not executed yet). If the upstream is in the online-DDL process, the precheck returns an error. In this case, wait until the DDL to complete and retry.

### Check items for full and incremental data migration
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 @@ -294,7 +294,7 @@ To use DM, you need to deploy a set of DM services either with a [TiUP cluster](

### Step 1. Prepare

Make sure that binlogs are enabled on MariaDB and that the `binlog_format` is set to `ROW`. It is also recommended to set `binlog_annotate_row_events=OFF` and `log_bin_compress=OFF`.
Enable binlog on MariaDB and set `binlog_format=ROW`, `binlog_row_image=FULL`, and `binlog_legacy_event_pos=ON`. Also set `binlog_annotate_row_events=OFF` and `log_bin_compress=OFF`.

You also need an account with the `SUPER` permission or with the `BINLOG MONITOR` and `REPLICATION MASTER ADMIN` permissions. This account also needs read permission for the schemas you are going to migrate.

Expand Down
Loading