Release Notes#

#v4.4.4

This is a patch release for the 4.4 line. It contains an important instance-creation fix, other bug fixes, a product name change, and updated base images; there are no new features.

#Product Name Change

Alauda Database Service for MySQL is now named Alauda Data Services Relational Database E1.

This is a display-name change only. The plugin package, its APIs and resource types, image names, configuration parameters, metric names, and log formats are unchanged, and no action is required when upgrading. Existing instances are unaffected.

The companion slow-query plugin has likewise been renamed to Alauda Data Services Query Analytics.

#Fixed Issues

#Instance Creation

• Fixed an issue where creating a MySQL instance failed with ImagePullBackOff on the agent sidecar, even though the operator itself installed successfully. The release pipeline recorded an agent image tag that was never mirrored into the customer registry, so the image did not exist on the target cluster. Any instance created on v4.3.3, v4.3.4, or v4.4.1 is affected; upgrade to v4.4.4 (or v4.3.5 on the 4.3 line) to resolve it. Instances already running are not affected.

#Instance Lifecycle

• Fixed an issue where recreating a MySQL instance with the same name shortly after deleting it left the new instance permanently not ready. The new instance adopted the previous instance's internal password secret, so it kept the old root credential and Group Replication could never be bootstrapped. The failure surfaced as an unready agent rather than as a credential error.
• Fixed a crash in persistent volume claim synchronization that could stop an instance from being reconciled.

#Console

• Corrected the supported MySQL version shown on the operator details page, which stated MySQL 8.0 while the 4.4 line creates MySQL 8.4 instances. The marketplace listing already showed the correct version.

#Query Analytics

Alauda Data Services Query Analytics is released alongside this version and has no separate release notes.

• Fixed an issue where the slow-query report and metrics pages returned an internal server error for an instance that had not yet reported any slow queries, or whose data had been cleaned up. These requests now return an empty result.
• Fixed an issue on Alauda Container Platform 4.4 where slow-query requests returned HTTP 404 because the plugin's ingress route was rewritten incorrectly. (Released in Query Analytics v4.4.1.)

#Security Fixes

• The MySQL server, router, and client images were rebuilt on a refreshed AlmaLinux 10 base image, upgrading openssl, openssl-libs, and libevent to versions that resolve the reported vulnerabilities.
• The mysqld-exporter image was rebuilt with an updated golang.org/x/crypto.
• The operator image was rebuilt on the refreshed client base image, and its gRPC dependency was updated.
• The slow-query components now ship the released build of the slow-query agent.

At release, the operator, MySQL server, MySQL router, monitoring exporter, and slow-query images scan to 0 HIGH and 0 CRITICAL vulnerabilities across 1,017 analyzed packages, against the Trivy vulnerability database of 2026-09-18. Counts are distinct CVEs. Scanning covers operating-system and language packages; the bundle image contains no packages and the console image's payload is not covered by package scanning, so neither contributes to that figure.

#Known Issues

#CPU requirement

The 4.4 line requires a processor supporting the x86-64-v3 microarchitecture level (Intel Haswell, AMD Excavator, or later). On older processors the operator and the MySQL server, router, and client containers abort at start with Fatal glibc error: CPU does not support x86-64-v3.

This requirement comes from the AlmaLinux 10 base image these components are built on and applies to the whole 4.4 line, from v4.4.0 onward; a patch release cannot lower it. The monitoring exporter is not affected. On hardware that does not meet this requirement, use the 4.3 line.

No issues in this release.

#v4.4.1

This is a patch release for the 4.4 line. It contains bug fixes and updated base images; there are no new features.

#Fixed Issues

#Cross-Cluster Disaster Recovery

• Fixed an issue where a MySQL cluster with cross-cluster replication over a host port could fail to finish forming, because the address a member advertised to its peer cluster was also used as the Group Replication local address.
• Fixes for cross-cluster disaster recovery address handling are now included in released builds. Previously these fixes existed only on the development branch, so no released version of the operator carried them.
• Fixed an issue where a failure while joining a replica cluster to a ClusterSet was neither reported nor retried with backoff, leaving the replica cluster in a half-initialized state.
• Fixed an issue where IPv6 addresses were parsed and assembled incorrectly on the cross-cluster replication path, so an IPv6 ClusterSet seed address could not be reached.
• Fixed an issue where creating a replica cluster timed out after 30 seconds, which interrupted the initial data clone on any cluster holding a non-trivial amount of data.
• Cross-cluster replication over a host port now verifies that Group Replication uses the MySQL communication stack, and reports a clear error instead of hanging when it does not.
• Fixed an issue where the operator could not tell an unreachable ClusterSet apart from a cluster that is not part of a ClusterSet, because the status query returned an empty result instead of an error when every member failed.

#Storage

• Fixed an issue where MySQL instances failed to start on storage classes whose volume root directory is not writable by the MySQL user, such as Ceph RBD and NFS CSI. The pod security context now sets fsGroup so that data directory ownership is applied when the volume is mounted.

#Backup

• Fixed an issue where a full logical backup (mysqlsh) could fail on MySQL instances containing partitioned tables.

#Security Fixes

• The MySQL server, router, and client images were rebuilt on an updated AlmaLinux 10 base image, upgrading openssl-libs and the bind-* packages to versions that resolve the reported vulnerabilities.
• The mysqld-exporter image was rebuilt on an updated Alpine base image, upgrading the OpenSSL libraries (libcrypto3 / libssl3) to versions that resolve the reported vulnerabilities.

#Known Issues

No issues in this release.

#v4.4.0

#New and Optimized Features

#MySQL 8.4 Support

MySQL-MGR clusters can now run MySQL 8.4, the latest long-term-support release (shipped with MySQL 8.4.8). New instances can be created directly on 8.4, and the parameter templates, monitoring, backup/restore, and router routing are all adapted to the 8.4 server. MySQL-MGR continues to support the single-primary and multi-primary Group Replication topologies on 8.4.

#In-Place Upgrade from MySQL 8.0 to 8.4

You can now upgrade an existing MySQL 8.0 MGR cluster in place to MySQL 8.4 without rebuilding the cluster or migrating data. The operator performs a rolling, member-by-member upgrade that:

• preserves all data and the existing Group Replication membership;
• upgrades the InnoDB Cluster metadata schema automatically;
• keeps the cluster serving traffic through MySQL Router during the rolling restart;
• reconciles members that are not yet in a safe replication-consistency state before proceeding, so the upgrade is safe even from a mixed starting state.

The upgrade is triggered through the standard version-upgrade flow on the instance. See Upgrade MySQL 8.0 to 8.4 for prerequisites and the full procedure.

#Fixed Issues

• Fixed an issue where a full logical backup (mysqlsh) could fail on MySQL instances containing partitioned tables.

#Known Issues

No issues in this release.