Stay organized with collections
Save and categorize content based on your preferences.
Managed Service for Apache Kafka requires each cluster to have equal resources in each
of the three zones. Single-zone or two-zone Managed Service for Apache Kafka clusters
are not supported.
You cannot choose the zones when you create the cluster.
You cannot configure the volume of local storage on a cluster.
Managed Service for Apache Kafka runs in the
KRaft mode.
Zookeeper mode is not supported.
JMX APIs for metrics are not supported.
Topic compression with zstd is not supported. Supported values
for compression.type include lz4, gzip, snappy, and uncompressed.
While you can change broker
configurations with read-only update mode at any time, these changes
take effect only when the brokers restart. Restarts happen periodically as part
of Google's maintenance and upgrade processes, but there's no set schedule or a
way to manually trigger them. As a result, you can't control when
these changes take effect. Examples of read-only configurations include
auto.create.topics.enable and background.threads.
Updates to configurations with the cluster-wide update mode, such as
message.max.bytes, don't require restarts and take effect immediately.
Some broker configuration parameters are managed by the service
and cannot be updated. This includes
broker.id and storage-related settings, such as
remote.log.storage.system.enable.
Apache Kafka® is a registered
trademark of The Apache Software Foundation or its affiliates in the United
States and/or other countries.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Managed Service for Apache Kafka limitations\n\n- Managed Service for Apache Kafka requires each cluster to have equal resources in each\n of the three zones. Single-zone or two-zone Managed Service for Apache Kafka clusters\n are not supported.\n\n- You cannot choose the zones when you create the cluster.\n\n- You cannot configure the volume of local storage on a cluster.\n\n- Managed Service for Apache Kafka runs in the\n [KRaft mode](https://kafka.apache.org/documentation/#kraft).\n Zookeeper mode is not supported.\n\n- JMX APIs for metrics are not supported.\n\n- Topic compression with `zstd` is not supported. Supported values\n for `compression.type` include `lz4`, `gzip`, `snappy`, and `uncompressed`.\n\n- While you can change broker\n configurations with `read-only` update mode at any time, these changes\n take effect only when the brokers restart. Restarts happen periodically as part\n of Google's maintenance and upgrade processes, but there's no set schedule or a\n way to manually trigger them. As a result, you can't control when\n these changes take effect. Examples of `read-only` configurations include\n `auto.create.topics.enable` and `background.threads`.\n Updates to configurations with the `cluster-wide` update mode, such as\n `message.max.bytes`, don't require restarts and take effect immediately.\n\n- Some broker configuration parameters are managed by the service\n and cannot be updated. This includes\n `broker.id` and storage-related settings, such as\n `remote.log.storage.system.enable`.\n\n*Apache Kafka® is a registered\ntrademark of The Apache Software Foundation or its affiliates in the United\nStates and/or other countries.*"]]
