30.3. Downgrading Kafka when using ZooKeeper


If you are using Kafka in ZooKeeper mode, the downgrade process involves changing the Kafka version and the related log.message.format.version and inter.broker.protocol.version properties.

30.3.1. Kafka version compatibility for downgrades

Kafka downgrades are dependent on compatible current and target Kafka versions, and the state at which messages have been logged.

You cannot revert to the previous Kafka version if that version does not support any of the inter.broker.protocol.version settings which have ever been used in that cluster, or messages have been added to message logs that use a newer log.message.format.version.

The inter.broker.protocol.version determines the schemas used for persistent metadata stored by the broker, such as the schema for messages written to __consumer_offsets. If you downgrade to a version of Kafka that does not understand an inter.broker.protocol.version that has ever been previously used in the cluster the broker will encounter data it cannot understand.

If the target downgrade version of Kafka has:

  • The same log.message.format.version as the current version, the Cluster Operator downgrades by performing a single rolling restart of the brokers.
  • A different log.message.format.version, downgrading is only possible if the running cluster has always had log.message.format.version set to the version used by the downgraded version. This is typically only the case if the upgrade procedure was aborted before the log.message.format.version was changed. In this case, the downgrade requires:

    • Two rolling restarts of the brokers if the interbroker protocol of the two versions is different
    • A single rolling restart if they are the same

Downgrading is not possible if the new version has ever used a log.message.format.version that is not supported by the previous version, including when the default value for log.message.format.version is used. For example, this resource can be downgraded to Kafka version 3.7.0 because the log.message.format.version has not been changed:

apiVersion: kafka.strimzi.io/v1beta2
kind: Kafka
spec:
  # ...
  kafka:
    version: 3.8.0
    config:
      inter.broker.protocol.version: "3.7"
      log.message.format.version: "3.7"
      # ...

The downgrade would not be possible if the log.message.format.version was set at "3.8" or a value was absent, so that the parameter took the default value for a 3.8.0 broker of 3.8.

重要

From Kafka 3.0.0, when the inter.broker.protocol.version is set to 3.0 or higher, the log.message.format.version option is ignored and doesn’t need to be set.

Downgrade a ZooKeeper-based Kafka cluster to an earlier version. When downgrading a ZooKeeper-based Kafka cluster to a lower version, like moving from 3.8.0 to 3.7.0, ensure that the inter-broker protocol version used by the Kafka cluster is a version supported by the Kafka version you want to downgrade to. The inter-broker protocol version for the Kafka version you are downgrading from must not be higher than the version you are downgrading to.

注意

Consult the Apache Kafka documentation for information regarding the support and limitations associated with ZooKeeper-based downgrades.

Prerequisites

  • The Cluster Operator is up and running.
  • Before you downgrade the Kafka cluster, check the following for the Kafka resource:

    • IMPORTANT: Compatibility of Kafka versions.
    • The Kafka custom resource does not contain options that are not supported by the Kafka version being downgraded to.
    • Kafka.spec.kafka.config has a log.message.format.version and inter.broker.protocol.version that is supported by the Kafka version being downgraded to.

      From Kafka 3.0.0, when the inter.broker.protocol.version is set to 3.0 or higher, the log.message.format.version option is ignored and doesn’t need to be set.

Procedure

  1. Update the Kafka cluster configuration.

    oc edit kafka <kafka_configuration_file>
  2. Change the inter.broker.protocol.version version (and log.message.format.version, if applicable) to a version supported by the Kafka version you are downgrading to; leave the Kafka.spec.kafka.version unchanged at the current Kafka version.

    For example, if downgrading from Kafka 3.8.0 to 3.7.0:

    apiVersion: kafka.strimzi.io/v1beta2
    kind: Kafka
    metadata:
      name: my-cluster
    spec:
      # ...
      kafka:
        version: 3.8.0 
    1
    
        config:
          inter.broker.protocol.version: "3.7" 
    2
    
          log.message.format.version: "3.7"
          # ...
    1
    Kafka version is unchanged.
    2
    Inter-broker protocol version is changed to a version supported by the earlier Kafka version.
    注意

    The value of log.message.format.version and inter.broker.protocol.version must be strings to prevent them from being interpreted as floating point numbers.

  3. Save and exit the editor, then wait for rolling updates to complete.

    Check the progress of the rolling updates by watching the pod state transitions:

    oc get pods my-cluster-kafka-0 -o jsonpath='{.spec.containers[0].image}'

    The rolling updates ensure that each pod is using the specified Kafka inter-broker protocol version.

  4. Change the Kafka.spec.kafka.version to the previous version.

    For example, if downgrading from Kafka 3.8.0 to 3.7.0:

    apiVersion: kafka.strimzi.io/v1beta2
    kind: Kafka
    metadata:
      name: my-cluster
    spec:
      # ...
      kafka:
        version: 3.7.0 
    1
    
        config:
          inter.broker.protocol.version: "3.7" 
    2
    
          log.message.format.version: "3.7"
          # ...
    1
    Kafka version is changed to the new version.
    2
    Inter-broker protocol version is supported by the Kafka version.
  5. If the image for the Kafka version is different from the image defined in STRIMZI_KAFKA_IMAGES for the Cluster Operator, update Kafka.spec.kafka.image.

    See 第 29.2.3 节 “Kafka version and image mappings”.

  6. Wait for the Cluster Operator to update the cluster.

    You can check the downgrade has completed successfully from the status of the Kafka resource.

  7. Downgrade all client applications (consumers) to use the previous version of the client binaries.

    The Kafka cluster and clients are now using the previous Kafka version.

  8. If you are reverting back to a version of Streams for Apache Kafka earlier than 1.7, which uses ZooKeeper for the storage of topic metadata, delete the internal topic store topics from the Kafka cluster.

    oc run kafka-admin -ti --image=registry.redhat.io/amq-streams/kafka-38-rhel9:2.8.0 --rm=true --restart=Never -- ./bin/kafka-topics.sh --bootstrap-server localhost:9092 --topic __strimzi-topic-operator-kstreams-topic-store-changelog --delete && ./bin/kafka-topics.sh --bootstrap-server localhost:9092 --topic __strimzi_store_topic --delete
Red Hat logoGithubRedditYoutubeTwitter

学习

尝试、购买和销售

社区

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

关于红帽文档

Legal Notice

Theme

© 2026 Red Hat
返回顶部