DM 5.3.0 Release Notes

Release date: November 30, 2021

DM version: 5.3.0

Special Notes

In earlier versions (v1.0 and v2.0), DM uses version numbers that are independent of TiDB. Since v5.3, DM uses the same version number as TiDB. The next version of DM v2.0 is DM v5.3. There are no compatibility changes from DM v2.0 to v5.3, and the upgrade process is no different from a normal upgrade, only an increase in version number.

Improvements

• Reduce latency when Relay Log is enabled #2225
• Compress/merge DML statements for incremental replication to reduce replication latency #3162 #3167
• Support OpenAPI feature to better manage DM clusters (experimental feature) #1928
• Optimize the user experience of dmctl and add subcommands #1746
• Support for maintaining transaction atomicity when stopping or pausing replication tasks #1928
• Support for reading Relay Log files with file names longer than 999999 #1933
• Load and sync units support more monitoring metrics #1778
• Support for concurrently manipulating tasks via dmctl #1995
• Optimize DML concurrency for incremental replication #2043
• Prompt user when HTTP proxy-related environment variables are detected #1960
• Optimize log display when handling RowEvent #2006
• Optimize log display when SQL execution is too slow #2024
• Optimize logic for fetching status data from upstream sources to reduce pressure on upstream #2076
• Report errors and prompt users when encountering unsupported binlog formats #2099
• Support for batch manipulation of all sync tasks in a data source via dmctl #2166
• Generate DML WHERE statements from downstream table schemas #3168
• Support for automatic acquisition and configuration of upstream and downstream time zones #3403

Bug fixes

• Fix the issue of high availability scheduling failure when configuring SSL certificates upstream and downstream #1910
• Fix the issue that pausing tasks takes too much time #1945
• Fix the issue that handle-error revert returns unclear error messages #1969
• Fix the issue that a replication task fails when you use binlog filter to skip certain DDL #1975
• Fix the issue that evict-leader fails in certain circumstances #1986
• Fix the issue that dmctl returns unclear error messages #2063
• Fix the issue of DM-worker scheduling failure when Relay Log is enabled #2199
• Fix the issue that DM-worker fails to connect to the upstream database and to start when Relay Log is enabled #2227
• Fix the issue of a meta file writing failure when Relay Log is enabled and upstream database switches #3164

Known issues

GitHub issues