DM: upgrade failed with event type truncate not valid #10282
Labels
affects-5.4
This bug affects the 5.4.x(LTS) versions.
affects-6.1
This bug affects the 6.1.x(LTS) versions.
affects-6.5
This bug affects the 6.5.x(LTS) versions.
affects-7.1
This bug affects the 7.1.x(LTS) versions.
affects-7.5
This bug affects the 7.5.x(LTS) versions.
area/dm
Issues or PRs related to DM.
report/customer
Customers have encountered this bug.
severity/critical
type/bug
The issue is confirmed as a bug.
What did you do?
upgrade dm from v5.3.0 to v6.5.3
What did you expect to see?
upgrade succeed
What did you see instead?
upgrade failed with
in binlog event filter: event type truncate not valid
Versions of the cluster
DM version (run
dmctl -V
ordm-worker -V
ordm-master -V
):(paste DM version here, and you must ensure versions of dmctl, DM-worker and DM-master are same)
Upstream MySQL/MariaDB server version:
(paste upstream MySQL/MariaDB server version here)
Downstream TiDB cluster version (execute
SELECT tidb_version();
in a MySQL client):(paste TiDB cluster version here)
How did you deploy DM: tiup or manually?
(leave TiUP or manually here)
Other interesting information (system version, hardware config, etc):
current status of DM cluster (execute
query-status <task-name>
in dmctl)(paste current status of DM cluster here)
The text was updated successfully, but these errors were encountered: