Databases 4 min read

DTLE 2.19.07.0 Release Notes – Features, Improvements, and Bug Fixes

The DTLE 2.19.07.0 release introduces cross‑data‑center transfer, cloud synchronization, data aggregation, subscription, bidirectional replication, performance improvements such as reduced CPU usage and tracing, and a series of bug fixes including connection leaks, NATS address handling, large‑transaction handling, and MySQL 8.0 compatibility warnings.

Aikesheng Open Source Community
Aikesheng Open Source Community
Aikesheng Open Source Community
DTLE 2.19.07.0 Release Notes – Features, Improvements, and Bug Fixes

DTLE 2.19.07.0 was released on August 14 as the latest open‑source data transfer component targeting MySQL and supporting multiple usage scenarios.

Project Overview

DTLE aims to ensure high‑quality data transmission, adapt to complex environments, and provide diverse functions for MySQL applications.

Key Capabilities

Cross‑data‑center reliable transfer with link compression to lower costs.

Cloud‑to‑cloud data sync/migration for disaster recovery.

Data aggregation from multiple sources into a single sink for analysis or dump.

Data subscription by pushing change events to Kafka or other middleware.

Bidirectional replication across data centers to enable dual‑write scenarios.

Official Resources

Project: https://github.com/actiontech/dtle

Documentation: https://actiontech.github.io/dtle-docs-cn/

Download: https://github.com/actiontech/dtle/releases (recommended to use the latest release tarball; source code available for custom builds).

Improvements / Features

Reduced CPU usage during full‑data copy process (issue #402).

Added tracing mechanism to locate performance problems (issue #477).

Bug Fixes

Fixed connection leakage after job removal (issue #41).

Correct usage of BindAddr and AdvertiseAddr for NATS (issues #452, #367).

Cleared residual error messages after job resume (issue #479).

Handled immediate failure when used with MySQL 8.0 (note: MySQL 8.0 not yet fully tested).

Job now fails gracefully instead of OOM crash when a transaction is too large (issue #462).

Resolved several table renaming (mapping) issues (issues #461, #470).

For the full original release notes, see the GitHub releases page linked above.

MySQLopen-sourcedatabasesdata transferRelease NotesDTLE
Aikesheng Open Source Community
Written by

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.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.