Data Migration 简单使用场景
本文介绍了 DM 工具的一个简单使用场景(非分库分表合并场景):将三个上游 MySQL 实例的数据迁移到一个下游 TiDB 集群中。
上游实例
假设上游结构为:
实例 1
Schema Tables user information, log store store_bj, store_tj log messages 实例 2
Schema Tables user information, log store store_sh, store_sz log messages 实例 3
Schema Tables user information, log store store_gz, store_sz log messages
迁移要求
不合并
user
库。将实例 1 中的
user
库迁移到下游 TiDB 的user_north
库中。将实例 2 中的
user
库迁移到下游 TiDB 的user_east
库中。将实例 3 中的
user
库迁移到下游 TiDB 的user_south
库中。任何情况下都不删除
log
表的任何数据。
将上游
store
库迁移到下游store
库中,且迁移过程中不合并表。实例 2 和实例 3 中都存在
store_sz
表,且这两个store_sz
表分别被迁移到下游的store_suzhou
表和store_shenzhen
表中。任何情况下都不删除
store
库的任何数据。
log
库需要被过滤掉。
下游实例
假设下游结构为:
Schema | Tables |
---|---|
user_north | information, log |
user_east | information, log |
user_south | information, log |
store | store_bj, store_tj, store_sh, store_suzhou, store_gz, store_shenzhen |
迁移方案
为了满足迁移要求中第一点的前三条要求,需要配置以下 table routing 规则:
routes: ... instance-1-user-rule: schema-pattern: "user" target-schema: "user_north" instance-2-user-rule: schema-pattern: "user" target-schema: "user_east" instance-3-user-rule: schema-pattern: "user" target-schema: "user_south"为了满足迁移要求中第二点的第一条要求,需要配置以下 table routing 规则:
routes: ... instance-2-store-rule: schema-pattern: "store" table-pattern: "store_sz" target-schema: "store" target-table: "store_suzhou" instance-3-store-rule: schema-pattern: "store" table-pattern: "store_sz" target-schema: "store" target-table: "store_shenzhen"为了满足迁移要求中第一点的第四条要求,需要配置以下 binlog event filter 规则:
filters: ... log-filter-rule: schema-pattern: "user" table-pattern: "log" events: ["truncate table", "drop table", "delete"] action: Ignore user-filter-rule: schema-pattern: "user" events: ["drop database"] action: Ignore为了满足迁移要求中第二点的第二条要求,需要配置以下 binlog event filter 规则:
filters: ... store-filter-rule: schema-pattern: "store" events: ["drop database", "truncate table", "drop table", "delete"] action: Ignore为了满足迁移要求中的第三点要求,需要配置以下 block & Allow Table Lists 规则:
block-allow-list: # 如果 DM 版本 <= v1.0.6 则使用 black-white-list log-ignored: ignore-dbs: ["log"]
迁移任务配置
以下是完整的迁移任务配置,详见配置介绍。
name: "one-tidb-slave"
task-mode: all
meta-schema: "dm_meta"
remove-meta: false
target-database:
host: "192.168.0.1"
port: 4000
user: "root"
password: ""
mysql-instances:
-
source-id: "instance-1"
route-rules: ["instance-1-user-rule"]
filter-rules: ["log-filter-rule", "user-filter-rule" , "store-filter-rule"]
block-allow-list: "log-ignored" # 如果 DM 版本 <= v1.0.6 则使用 black-white-list
mydumper-config-name: "global"
loader-config-name: "global"
syncer-config-name: "global"
-
source-id: "instance-2"
route-rules: ["instance-2-user-rule", instance-2-store-rule]
filter-rules: ["log-filter-rule", "user-filter-rule" , "store-filter-rule"]
block-allow-list: "log-ignored" # 如果 DM 版本 <= v1.0.6 则使用 black-white-list
mydumper-config-name: "global"
loader-config-name: "global"
syncer-config-name: "global"
-
source-id: "instance-3"
route-rules: ["instance-3-user-rule", instance-3-store-rule]
filter-rules: ["log-filter-rule", "user-filter-rule" , "store-filter-rule"]
block-allow-list: "log-ignored" # 如果 DM 版本 <= v1.0.6 则使用 black-white-list
mydumper-config-name: "global"
loader-config-name: "global"
syncer-config-name: "global"
# 所有实例的共有配置
routes:
instance-1-user-rule:
schema-pattern: "user"
target-schema: "user_north"
instance-2-user-rule:
schema-pattern: "user"
target-schema: "user_east"
instance-3-user-rule:
schema-pattern: "user"
target-schema: "user_south"
instance-2-store-rule:
schema-pattern: "store"
table-pattern: "store_sz"
target-schema: "store"
target-table: "store_suzhou"
instance-3-store-rule:
schema-pattern: "store"
table-pattern: "store_sz"
target-schema: "store"
target-table: "store_shenzhen"
filters:
log-filter-rule:
schema-pattern: "user"
table-pattern: "log"
events: ["truncate table", "drop table", "delete"]
action: Ignore
user-filter-rule:
schema-pattern: "user"
events: ["drop database"]
action: Ignore
store-filter-rule:
schema-pattern: "store"
events: ["drop database", "truncate table", "drop table", "delete"]
action: Ignore
block-allow-list: # 如果 DM 版本 <= v1.0.6 则使用 black-white-list
log-ignored:
ignore-dbs: ["log"]
mydumpers:
global:
threads: 4
chunk-filesize: 64
skip-tz-utc: true
loaders:
global:
pool-size: 16
dir: "./dumped_data"
syncers:
global:
worker-count: 16
batch: 100
max-retry: 100