dm loss upstream table structure when enter sync stage and failed immediately #7159
Labels
affects-5.3
affects-5.4
This bug affects the 5.4.x(LTS) versions.
affects-6.0
affects-6.1
This bug affects the 6.1.x(LTS) versions.
affects-6.2
affects-6.3
area/dm
Issues or PRs related to DM.
severity/minor
type/bug
The issue is confirmed as a bug.
What did you do?
start an all mode task, and failed when enter sync stage immediately
What did you expect to see?
operate-schema get
return upstream table infoWhat did you see instead?
operate-schema get
return downstream table infoVersions 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: