Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
  • Blog
  • Pricing
  • Documentation
Yandex project
© 2025 Yandex.Cloud LLC
Yandex Managed Service for MySQL®
  • Getting started
    • Resource relationships
    • Network in Managed Service for MySQL
    • Quotas and limits
    • Disk types
    • Backups
    • Replication
    • Maintenance
    • User permissions
    • MySQL settings
    • SQL command limits
    • Comparing MySQL® 5.7 and 8.0
  • Access management
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes

In this article:

  • Maintenance window
  • Maintenance procedure
  1. Concepts
  2. Maintenance

Maintenance in Managed Service for MySQL®

Written by
Yandex Cloud
Updated at January 23, 2025
  • Maintenance window
  • Maintenance procedure

In Managed Service for MySQL®, maintenance means:

  • Automatic installation of DBMS updates and fixes for hosts (including for disabled clusters).
  • Other maintenance activities.

Changing a DBMS version is not part of maintenance. For more information about version changes, see MySQL® version upgrade.

Maintenance windowMaintenance window

You can set the preferred maintenance time when creating a cluster or updating its settings:

  • The arbitrary option (default) allows performing maintenance at any time.
  • The by schedule option allows setting the preferred maintenance start day and time (UTC). For example, you can choose a time when the cluster is least loaded.

Maintenance procedureMaintenance procedure

In Managed Service for MySQL® single-host clusters, a master host undergoes maintenance. Therefore, it may become unavailable in case it is restarted.

In multi-host clusters, the maintenance is run as follows:

  1. Replicas undergo maintenance one by one. The replicas are queued randomly. A replica becomes temporarily unavailable if it needs to be restarted during maintenance.
  2. Master host undergoes maintenance and gets updated. If it is restarted and becomes unavailable, one of the replicas takes its role. If you access a cluster using the FQDN of the master host, the cluster may become unavailable. To make your application continuously available, access the cluster using a special FQDN that always points to the master host.

Was the article helpful?

Previous
Replication
Next
User permissions
Yandex project
© 2025 Yandex.Cloud LLC