Apache Kafka 2.4.0 Release: New Features and Improvements
Apache Kafka 2.4.0 introduces a range of new capabilities—including consumer replica fetching, incremental cooperative rebalancing, MirrorMaker 2.0, a new Java authorization API, KTable non‑key joins, administrative replica reassignment, protected REST endpoints, and offset deletion—along with numerous performance and stability improvements.
Apache Kafka version 2.4.0 has been released, introducing several new capabilities and enhancements.
Consumers can fetch from the latest replica.
Support for incremental cooperative rebalancing in the Consumer Rebalance Protocol.
Introduction of MirrorMaker 2.0 (MM2), a new multi‑cluster cross‑data‑center replication engine.
New Java authorization API.
Support for non‑key joins in KTable.
Administrative API for replica reassignment.
Protection of internal REST endpoints.
API to delete consumer offsets exposed via AdminClient.
Improvements:
[KAFKA-5609] Log4j connection now logs to a file by default.
[KAFKA-6263] Metrics exposed for group metadata load duration.
[KAFKA-6883] KafkaShortnamer can convert Kerberos principal names to uppercase usernames.
[KAFKA-6958] Allow custom processor names in KStreams DSL.
[KAFKA-7018] Persistent memberId usage for consumer restarts.
[KAFKA-7149] Reduced assignment data size to improve Kafka stream scalability.
[KAFKA-7190] WARN about UNKNOWN_PRODUCER_ID when clearing partition topics under heavy traffic.
[KAFKA-7197] Upgrade to Scala 2.13.0.
For the full list of changes, visit the Confluent blog post at https://www.confluent.io/blog/apache-kafka-2-4-latest-version-updates/ .
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Big Data Technology & Architecture
Wang Zhiwu, a big data expert, dedicated to sharing big data technology.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.