DTLE 3.21.10.0 Release Notes – New Features and Updates
The DTLE 3.21.10.0 release introduces foreign‑key support, a new job parameter for foreign key checks, cascade operations, handling of large‑memory transactions, and various bug fixes and refactorings, providing a more robust MySQL data‑transfer solution.
Version 3.21.10.0
DTLE (Data Transfer Layer Engine) 3.21.10.0 has been released. DTLE is an open‑source data‑transfer component designed for MySQL, aiming to ensure high‑quality data transmission, adapt to complex scenarios, and offer diverse functionalities.
Project Links
Type
URL
Repository
https://github.com/actiontech/dtle
Documentation
https://actiontech.github.io/dtle-docs-cn/
Release Information
https://github.com/actiontech/dtle/releases
Tip: It is recommended to download the latest release. For RHEL/CentOS, use the RPM package; for other Linux distributions, download the tarball or run via Docker.
Update List
Release Notes – New Features
Foreign Key support (issue #795)
Preliminary support for transactions larger than available memory
Other Changes
For transactions that cannot use writeset, fallback to MySQL’s last_commit value
Various code clean‑up and refactoring
Recommended Reading
Data Transfer | How DTLE Configures Failover Domains
Data Transfer | DTLE Parallel Replay Performance Test Report
Data Transfer | Introduction to Using DTLE
For more articles about DTLE, follow the public account menu “Community Information – Open‑Source Products”.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Aikesheng Open Source Community
The Aikesheng Open Source Community provides stable, enterprise‑grade MySQL open‑source tools and services, releases a premium open‑source component each year (1024), and continuously operates and maintains them.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.