# Yandex Managed Service for MySQL® release notes

## May 2026 {#may-2026}

* Added the ability to [create and restore](operations/cluster-backups.md) clusters with encrypted local disks from a backup. The encryption uses a custom KMS key.
* Maximum local disk size per host is increased to 36 TB. Disks of this size are available for Intel Ice Lake (`standard-v3`) configurations with 16 or more cores. To create extra large clusters, you may need to contact [support](https://center.yandex.cloud/support) to reserve the required resources.
* Published the updated [versioning policies](concepts/update-policy.md) describing in detail the periods and terms of support for various DBMS versions.
* Added the **Innodb adaptive hash index** setting that sets the number of InnoDB [adaptive hash index](https://dev.mysql.com/doc/refman/8.0/en/glossary.html#glos_adaptive_hash_index) settings. Partitioning reduces contention between threads and improves performance in highly parallel systems. For more information, see [MySQL® settings](concepts/settings-list.md).
* Added the **Max write lock count** setting that sets the maximum number of consecutive write locks allowed before the server starts processing pending read lock requests. For more information, see [MySQL® settings](concepts/settings-list.md).

## April 2026 {#apr-2026}

* Users with the `mdb.admin` [role](security/index.md#mdb-admin) can now [view the list](operations/cluster-users.md#list-users) of users they created via the `mysql.v_user`, `mysql.v_db`, and `mysql.v_procs_priv` views.
* Added protection against accidental database deletion, similar to cluster deletion protection.
* After a [maintenance operation](concepts/maintenance.md), the priority host automatically becomes the master again. This switching is performed when replication delay is under 10 seconds. If needed, the system waits for up to 30 minutes.

## March 2026 {#mar-2026}

* Added specific [roles](security/index.md) to view and edit (reschedule) [maintenance](concepts/maintenance.md) without access to the cluster.

## February 2026 {#feb-2026}

* New MySQL® minor versions are out: [8.4.7](https://docs.percona.com/percona-server/8.4/release-notes/8.4.7-7.html), [8.0.43](https://docs.percona.com/percona-server/8.0/release-notes/8.0.43-34.html), and [5.7.44-54](https://docs.percona.com/percona-server/5.7/release-notes/5.7.44-54.html). Cluster updates scheduled.

## December 2025 {#dec-2025}

* Added [detailed metrics](operations/monitoring.md#hosts) for disk usage on cluster hosts.
* Added execution details for [cluster operations](operations/cluster-list.md#list-operations).

## November 2025 {#nov-2025}

Added the `managed-mysql.restorer` role for restoring clusters from backups. To learn more, see [Access management](security/index.md#managed-mysql-restorer).

## October 2025 {#oct-2025}

* Increased the binary log size for clusters with large disks for quicker recovery of large clusters in case of failure.
* Added new [host classes](concepts/instance-types.md) on AMD Zen 4 and AMD Zen 4 HighFreq platforms.

## September 2025 {#sep-2025}

* A new major MySQL® version is out: [8.4.6](https://docs.percona.com/percona-server/8.4/release-notes/8.4.6-6.html). Upgrade is not yet available, it will be supported later.
* New MySQL® minor versions are out: [5.7.44-53](https://docs.percona.com/percona-server/5.7/release-notes/5.7.44-53.html) and [8.0.41](https://docs.percona.com/percona-server/8.0/release-notes/8.0.41-32.html).
* Now you can configure incremental [automatic expansion of your cluster storage](concepts/storage.md#disk-size-autoscaling). Users can set the disk storage usage threshold and the maximum disk size. Upon reaching the threshold, the disk size will automatically increase in fixed increments up to its maximum.
* Added a new [administrative privilege](concepts/settings-list.md#setting-administrative-privileges): `mdb_admin`.


## July 2025 {#jul-2025}

Now you can [encrypt storage disks](concepts/storage.md#disk-encryption) with a custom KMS key when creating a cluster and restoring it from a backup.


## April 2025 {#apr-2025}

Added [integration with Connection Manager](operations/update.md#conn-man). Now, a connection in Connection Manager is automatically created for all new clusters.

## October 2024 {#oct-2024}

Added support for [setting a retention period for automatic backups](operations/cluster-backups.md#set-backup-retain).


## September 2024 {#sep-2024}

Added the **Yandex Query access** option to cluster settings. It enables you to run YQL queries from [Yandex Query](../query/concepts/index.md) to a Yandex MPP Analytics for PostgreSQL database.


## May 2024 {#may-2024}

* New MySQL® versions are out: [5.7.44](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-44.html) and [8.0.35](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-35.html).

## Q4 2023 {#q4-2023}

* A new MySQL® version is out: [8.0.31](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-31.html).

## Q2 2023 {#q2-2023}

* New MySQL® versions are out: [5.7.39](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-39.html) and [8.0.30](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-30.html).
* MySQL® 5.7 now supports analyzing queries using `query_response_time_stats`. For more information, see [this Percona article](https://docs.percona.com/percona-server/5.7/diagnostics/response_time_distribution.html).
* Added new global user permissions: `FLUSH_OPTIMIZER_COSTS` and `SHOW_ROUTINE`.

## Q4 2022 {#q4-2022}

* The status of a host on the **Hosts** page in the management console now changes to `READ-ONLY` if data writes to the host are disabled.
* You can now [move a cluster](operations/update.md#move-cluster) to a different folder using Terraform.
* Added new DBMS settings:

  * `Backup retain period days`
  * [Lock wait timeout](concepts/settings-list.md#setting-lock-wait-timeout)
  * [Max prepared stmt count](concepts/settings-list.md#setting-max-prepared-stmt-count)
  * [Optimizer search depth](concepts/settings-list.md#setting-optimizer-search-depth)
  * [Optimizer switch](concepts/settings-list.md#setting-optimizer-switch)

## Q3 2022 {#q3-2022}

* Added the `Free space` chart to the [cluster monitoring](operations/monitoring.md#monitoring-cluster) tab and the `Inode usage` chart to the [host monitoring](operations/monitoring.md#monitoring-hosts) page.
* Added the [Binlog transaction dependency tracking](concepts/settings-list.md#setting-binlog-transaction-dependency-tracking) setting.

## Q2 2022 {#q2-2022}

* Removed the `database` and `user` sections in the Terraform configuration files and added the `yandex_mdb_mysql_database` and `yandex_mdb_mysql_user` resources instead.
* Added the [Innodb compression level](concepts/settings-list.md#setting-innodb-compression-level) setting.
* Accelerated replica restoration from a backup through WAL-G with subsequent synchronization of data from the master host.
* Fixed the display of long queries on the **Performance diagnostics** tab.

## Q1 2022 {#q1-2022}

* You can now edit the [Innodb strict mode](concepts/settings-list.md#setting-strict-mode), [Max digest length](concepts/settings-list.md#setting-max-digest-length), and [Max sp recursion depth](concepts/settings-list.md#setting-max-sp-recursion-depth) settings.
* Added a section for diagnostics of MySQL® cluster performance in Terraform.
* You can now manage the settings of the performance diagnostics service.
* Enhanced master failover logic: the system now prevents failover to a significantly lagging replica or when the quorum is missing. The maximum lag for a replica is defined by the [Mdb priority choice max lag](concepts/settings-list.md#setting-mdb-priority-choice-max-lag) setting.
* You can now set the master host failover priority.