Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex Managed Service for Apache Kafka®
  • Getting started
    • Resource relationships
    • Topics and partitions
    • Brokers
    • KRaft protocol
    • Producers and consumers
    • User roles
    • Managing data schemas
    • Web interface for Apache Kafka®
    • APIs in Managed Service for Apache Kafka®
    • Host classes
    • High availability clusters
    • Networking in Managed Service for Apache Kafka®
    • Quotas and limits
    • Storage in Managed Service for Apache Kafka®
    • Connectors
    • Maintenance
    • Apache Kafka® settings
    • Apache Kafka® versioning policy
  • Access management
  • Pricing policy
  • Terraform reference
  • Yandex Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes
  • FAQ

In this article:

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

Maintenance in Managed Service for Apache Kafka®

Written by
Yandex Cloud
Updated at October 28, 2025
  • Maintenance window
  • Maintenance procedure
  • Karapace availability

Maintenance means:

  • Automatic installation of Apache Kafka® updates and revisions for hosts (including disabled clusters).
  • Scheduled automatic increase of storage size.
  • Other maintenance activities.

Maintenance includes changes within one Apache Kafka® major version. For information about migrating between major versions, see Apache Kafka® 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 single-host Managed Service for Apache Kafka® clusters, a single broker host undergoes maintenance. This means, if a cluster needs to be restarted during maintenance, it will become unavailable.

In multi-host clusters, broker hosts undergo maintenance one by one. The 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.

Was the article helpful?

Previous
Connectors
Next
Apache Kafka® settings
© 2025 Direct Cursus Technology L.L.C.