Yandex Managed Service for MySQL® release notes

October 2024October 2024

Now you can specify a retention period for your automatic backups.

September 2024September 2024

Added the Yandex Query access option to cluster settings. It enables you to run YQL queries from Yandex Query to a Managed Service for Greenplum® database.

May 2024May 2024

• New MySQL® versions are now available: 5.7.44 and 8.0.35.

Q4 2023Q4 2023

• A new version is out: MySQL® 8.0.31.

Q2 2023Q2 2023

• New MySQL® versions are now available: 5.7.39 and 8.0.30.
• MySQL® 5.7 now supports analyzing queries using query_response_time_stats. For more information, see the Percona documentation.
• Added new global user permissions: FLUSH_OPTIMIZER_COSTS and SHOW_ROUTINE.

Q4 2022Q4 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 to a different folder using Terraform.

• Added new DBMS settings:

  • Backup retain period days
  • Lock wait timeout
  • Max prepared stmt count
  • Optimizer search depth
  • Optimizer switch

Q3 2022Q3 2022

• Added the Free space plot to the cluster monitoring tab and the Inode usage plot to the host monitoring page.
• Added the Binlog transaction dependency tracking setting.

Q2 2022Q2 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 setting.
• Accelerated the process of restoring replicas from a backup by using WAL-G with subsequent synchronization of data from the master host.
• Fixed the display of long queries on the Performance diagnostics tab.

Q1 2022Q1 2022

• You can now edit the Innodb strict mode, Max digest length, and 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.
• Updated the master failover mechanism: you can no longer switch to a replica that is lagging far behind or change the master if there is no quorum. The maximum lag for a replica is set by the Mdb priority choice max lag setting.
• You can now set a priority for selecting a master host if the master changes.