DTLE 3.20.09.0 Release Notes – New Monitoring Features, Docker Support, and Bug Fixes
Version 3.20.09.0 of the open‑source DTLE data‑transfer component for MySQL has been released, introducing replication‑delay and memory‑usage monitoring with Prometheus, providing configuration examples and Docker commands, and fixing incremental serialization, CPU usage, and uppercase‑where clause handling.
DTLE (Data Transfer Layer Engine) is an open‑source component designed for MySQL that aims to ensure reliable data transfer, adapt to complex scenarios, and offer a variety of functions.
Project Links 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; RPM packages are available for RHEL/CentOS, while tarballs or Docker images can be used on other Linux distributions.
New Features
The 3.20.09.0 release adds monitoring items for replication delay and memory usage. Details are available in the manual sections 3.4 and 3.11.
Replication delay monitoring
Memory usage monitoring
Prometheus Configuration Demo
Prometheus can be used to visualize the new metrics and store historical values. Below is a sample prometheus.yml configuration:
scrape_configs:
- job_name: 'dtle'
# Override the global default and scrape targets from this job every 5 seconds.
scrape_interval: 5s
static_configs:
- targets: ['127.0.0.1:8190','127.0.0.2:8190'] # Fill in the DTLE compatibility layer address; multiple entries are allowed.Run Prometheus with Docker using the following command:
docker run \
-p 9090:9090 \
-v ${PWD}/prometheus.yml:/etc/prometheus/prometheus.yml \
prom/prometheusAfter starting, open a browser at http://127.0.0.1:9090 to query the metrics.
For detailed metric definitions, refer to the manual sections:
Metrics for delay (3.4)
Metrics for memory (3.11)
Fixes
Replaced incremental sequence library to reduce CPU usage and improve performance.
Handled uppercase characters in the 'where' column (issue #523).
Release Notes Summary
New
Metrics for delay
Metrics for memory
Fixed
Use gencode instead of gob for incremental stage serialization, reducing CPU consumption.
Fix #523: handle uppercase in 'where' column.
Recommended reading: Data Transfer | DTLE Introduction
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.