Chapter 5. Kafka breaking changes


This section describes any changes to Kafka that required a corresponding change to Streams for Apache Kafka to continue to work.

5.1. ZooKeeper no longer supported

From Kafka 4.0, ZooKeeper is no longer supported. Kafka clusters must operate in KRaft mode.

5.2. Kafka MirrorMaker 1

Kafka MirrorMaker 1 has been removed in Kafka 4.0. MirrorMaker 2 is the only version available. MirrorMaker 2 is based on the Kafka Connect framework, connectors managing the transfer of data between clusters.

If you’re using MirrorMaker 1, you can replicate its functionality in MirrorMaker 2 by using the IdentityReplicationPolicy class. By default, MirrorMaker 2 renames topics replicated to a target cluster, but IdentityReplicationPolicy preserves the original topic names, enabling the same active/passive unidirectional replication as MirrorMaker 1.

5.3. Auto-include of JMXReporter removed

The auto.include.jmx.reporter configuration has been removed in Kafka. From Kafka 4.0, to enable the JMXReporter you must either enable metrics in .spec.kafka.metrics, or explicitly add JMXReporter in metric.reporters.

5.4. Log4j2 for logging

Logging framework has been migrated from Log4j to Log4j2. If you have any custom logging configuration, you might need to update it during the upgrade to Kafka 4.0.

Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat Documentation

Legal Notice

Theme

© 2026 Red Hat
Back to top