Maintenance in Managed Service for Apache Kafka®

Maintenance includes:

• Automatic installation of Apache Kafka® updates and patches for hosts (including for stopped clusters).
• Scheduled automatic storage expansion.
• Other maintenance activities.

Maintenance includes changes within one Apache Kafka® major version. Learn more about migrating between major versions here.

Maintenance windowMaintenance window

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

• The At any time option (default) allows performing maintenance at any time.
• The By schedule option allows you to select the day of the week and UTC time interval for the maintenance. For example, you can choose a time when the cluster is least loaded.

Both active and stopped clusters are subject to maintenance. Maintenance operations may include DBMS updates, applying patches, etc.

In the management console, you select the maintenance start time as an hour interval. In other interfaces, you specify this interval by its sequence number, from 1 to 24.

For example, to start maintenance in the interval from 00:00 to 01:00, put 1; from 04:00 to 05:00, 5.

Maintenance workflowMaintenance workflow

In single-host Managed Service for Apache Kafka® clusters, a single broker host undergoes maintenance. This means, if you restart such a cluster during maintenance, it will become unavailable.

In multi-host clusters, broker hosts undergo maintenance one by one. Such hosts are queued randomly. A broker host becomes unavailable while it is being restarted during maintenance.

Karapace availabilityKarapace availability

Karapace is unavailable during maintenance and automatically restarts after its completion. Meanwhile, all schema data is retained as it is stored in the __schema_registry service topic.

Learn more about managing data schemas.