- Overview
- Features
- Benchmark
- Usage Scenarios
- Quick Start
- Deploy
- Deploy a DM Cluster
- Migrate Data Using DM
- Configure
- Manage the DM Cluster
- Manage Migration Tasks
- Monitor
- Migrate from MySQL-compatible Database
- DM Portal
- Alert
- Troubleshoot
- FAQ
- Releases
- TiDB DM Glossary
Important
You are viewing the documentation for an older major version of the TiDB Data Migration tool (TiDB Data Migration v1.0).
TiDB Data Migration , the latest major version of TiDB Data Migration, is now stable and recommended for general use. To view this page for TiDB Data Migration , click here.
DM 1.0.4 Release Notes
Release date: March 13, 2020
DM version: 1.0.4
DM-Ansible version: 1.0.4
Improvements
- Add English UI for DM-portal
- Add the
--more
parameter in thequery-status
command to show complete migration status information
Bug fixes
- Fix the issue that
resume-task
might fail to resume the migration task which is interrupted by the abnormal connection to the downstream TiDB server - Fix the issue that the online DDL operation cannot be properly migrated after a failed migration task is restarted because the online DDL meta information has been cleared after the DDL operation failure
- Fix the issue that
query-error
might cause the DM-worker to panic afterstart-task
goes into error - Fix the issue that the relay log file and
relay.meta
cannot be correctly recovered when restarting an abnormally stopped DM-worker process beforerelay.meta
is successfully written
Detailed bug fixes and changes
- Add English UI for DM-portal #480
- Add the
--more
parameter in thequery-status
command to show complete migration status information #533 - Fix the issue that
resume-task
might fail to resume the migration task which is interrupted by the abnormal connection to the downstream TiDB server #436 - Fix the issue that the online DDL operation cannot be properly migrated after a failed migration task is restarted because the online DDL meta information is cleared after the DDL operation failure #465
- Fix the issue that
query-error
might cause the DM-worker to panic afterstart-task
goes into error #519 - Fix the issue that the relay log file and
relay.meta
cannot be correctly recovered when restarting an abnormally stopped DM-worker process beforerelay.meta
is successfully written #534 - Fix the issue that the
value out of range
error might be reported when gettingserver-id
from the upstream #538 - Fix the issue that when Prometheus is not configured DM-Ansible prints the wrong error message that DM-master is not configured #438
Was this page helpful?