DM 从上游分库迁移至下游tidb中存在少量重复数据

配置文件:
cat sharding_busi_detail.yaml
name: “sharding_busi_detail”
task-mode: “all”

target-database:
host: “172.17.x.xx”
port: xxxx
user: “root”
password: “n7NLD6TpEuGe4kEnVhgxy0Dr67IMIXA=”

routes:
route-rule-0:
schema-pattern: “calcdb0*”
target-schema: “calcdb”

route-rule-1:
schema-pattern: “calcdb0*”
table-pattern: “t_busi_detail”
target-schema: “calcdb”
target-table: “t_busi_detail”

filters:
filter-rule-0:
schema-pattern: “calcdb0*”
events: [“all dml”]
action: Do

filter-rule-1:
schema-pattern: “calcdb0*”
table-pattern: “t_busi_detail”
events: [“truncate table”, “drop table”]
sql-pattern: [“ALTER\s+TABLE[\s\S]*ADD\s+PARTITION”, “ALTER\s+TABLE[\s\S]*DROP\s+PARTITION”]
action: Ignore

mysql-instances:

source-id: “slave-mysql-x-xx-11851”
block-allow-list: “bw-rule-1”
route-rules: [“route-rule-0”, “route-rule-1”]
filter-rules: [“filter-rule-0”, “filter-rule-1”]

source-id: “slave-mysql-x-xx-11852”
block-allow-list: “bw-rule-1”
route-rules: [“route-rule-0”, “route-rule-1”]
filter-rules: [“filter-rule-0”, “filter-rule-1”]

source-id: “slave-mysql-x-xx-11853”
block-allow-list: “bw-rule-1”
route-rules: [“route-rule-0”, “route-rule-1”]
filter-rules: [“filter-rule-0”, “filter-rule-1”]

source-id: “slave-mysql-x-xx-11854”
block-allow-list: “bw-rule-1”
route-rules: [“route-rule-0”, “route-rule-1”]
filter-rules: [“filter-rule-0”, “filter-rule-1”]

source-id: “slave-mysql-x-xx-11855”
block-allow-list: “bw-rule-1”
route-rules: [“route-rule-0”, “route-rule-1”]
filter-rules: [“filter-rule-0”, “filter-rule-1”]

source-id: “slave-mysql-x-xx-11856”
block-allow-list: “bw-rule-1”
route-rules: [“route-rule-0”, “route-rule-1”]
filter-rules: [“filter-rule-0”, “filter-rule-1”]

source-id: “slave-mysql-x-xx-11857”
block-allow-list: “bw-rule-1”
route-rules: [“route-rule-0”, “route-rule-1”]
filter-rules: [“filter-rule-0”, “filter-rule-1”]

block-allow-list:
bw-rule-1:
do-dbs: [“calcdb0*”]
do-tables:
- db-name: “calcdb0*”
tbl-name: “t_busi_detail”

初始化完数据会停下来,应为下游多了一列,已上游表结构为准,操作如下:
tiup dmctl --master-addr 172.17.x.xxx:8261 binlog-schema update -s slave-mysql-x-xx-11851 sharding_busi_detail calcdb01 t_sub_account_busi_detail --from-source
tiup dmctl --master-addr 172.17.x.xxx:8261 binlog-schema update -s slave-mysql-x-xx-11852 sharding_busi_detail calcdb02 t_sub_account_busi_detail --from-source
tiup dmctl --master-addr 172.17.x.xxx:8261 binlog-schema update -s slave-mysql-x-xx-11853 sharding_busi_detail calcdb03 t_sub_account_busi_detail --from-source
tiup dmctl --master-addr 172.17.x.xxx:8261 binlog-schema update -s slave-mysql-x-xx-11854 sharding_busi_detail calcdb04 t_sub_account_busi_detail --from-source
tiup dmctl --master-addr 172.17.x.xxx:8261 binlog-schema update -s slave-mysql-x-xx-11855 sharding_busi_detail calcdb05 t_sub_account_busi_detail --from-source
tiup dmctl --master-addr 172.17.x.xxx:8261 binlog-schema update -s slave-mysql-x-xx-11856 sharding_busi_detail calcdb06 t_sub_account_busi_detail --from-source
tiup dmctl --master-addr 172.17.x.xxx:8261 binlog-schema update -s slave-mysql-x-xx-11857 sharding_busi_detail calcdb07 t_sub_account_busi_detail --from-source

tiup dmctl --master-addr 172.17.x.xxx:8261 resume-task sharding_busi_detail

tiup dmctl --master-addr 172.17.x.xxx:8261 check-task sharding_busi_detail.yaml