November 6, 2019 By Mickael Maison 2 min read

In this 21st edition of the Kafka Monthly Digest, I will cover what happened in the Kafka Community in October 2019.

For last month’s digest, see “Kafka Monthly Digest: September 2019.”


  • 2.3.1: This bugfix version was released on October 25, 2019 by David Arthur. It contains 46 fixes and improvements, including six blocker JIRAs. See the release notes for the full details.

There are still one bugfix release and one minor release in progress.

  • 2.2.2: After a couple of late bugs (KAFKA-9053, KAFKA-8649) related to Kafka Streams had been fixed, Randall Hauch prepared 2.2.2 RC2. The vote on this release candidate is currently ongoing. If no further issues are found, it should release in the next few days.
  • 2.4.0: The release process continued, and the code freeze happened on October 16, 2019. A few issues were found and there is currently one blocker left open (KAFKA-8677). The first release candidate should be available in the next few days.


Last month, the community submitted 17 KIPs (KIP-530 to KIP-546, 529 was skipped) and these are the ones that caught my eye:

KIP-531: Drop support for Scala 2.11 in Kafka 2.5: At the moment, Kafka builds for three Scala versions: 2.11, 2.12, and 2.13. The proposal is to stop building for 2.11 as this version has reached end of support. This will simplify the compatibility matrix and reduce development and tests costs. Finally, this will allow for taking advantage of more recent Scala features, especially around interoperability with Java 8 functional interfaces.

KIP-542: Partition Reassignment Throttling: Partition reassignments often cause significant load on a cluster. Since 0.10.1, quotas can be applied to control them, but these quotas also apply to existing replicas. The goal of this KIP is to allow for defining separate quotas for replication and reassignment. This will enable administrators to control reassignments without impacting regular replication.

KIP-543: Expand ConfigCommand’s non-ZK functionality: One of the pre-requirements to remove Zookeeper (KIP-500) is to update all tools to work without Zookeeper. At the moment, the kafka-configs tool still requires Zookeeper to update topic configurations and quotas. This KIP’s goal is to update this tool so it does not require on Zookeeper for any operations.

KIP-544: Make metrics exposed via JMX configurable: Kafka exposes a lot of metrics. In fact, in large clusters, monitoring agents can sometimes timeout while listing metrics. This KIP proposes adding configurations to the broker to blacklist or whitelist metrics. By also allowing to update these settings at runtime, administrators will be able to specify the metrics they want to omit, precisely.

KIP-545: support automated consumer offset sync across clusters in MM 2.0: MirrorMaker 2 added some tooling to translate consumer group offsets between clusters. This KIP aims to make failover between clusters even simpler by automatically populating the __consumer_offsets topics in downstream clusters. This will allow consumers to transparently find their new positions when switching clusters.


Get started

IBM Event Streams for Cloud is Apache Kafka-as-a-service for IBM Cloud.

Get started with IBM Event Streams

More from Announcements

IBM Hybrid Cloud Mesh and Red Hat Service Interconnect: A new era of app-centric connectivity 

2 min read - To meet customer demands, applications are expected to be performing at their best at all times. Simultaneously, applications need to be flexible and cost effective, and therefore supported by an underlying infrastructure that is equally reliant, performant and secure as the applications themselves.   Easier said than done. According to EMA's 2024 Network Management Megatrends report only 42% of responding IT professionals would rate their network operations as successful.   In this era of hyper-distributed infrastructure where our users, apps, and data…

IBM named a Leader in Gartner Magic Quadrant for SIEM, for the 14th consecutive time

3 min read - Security operations is getting more complex and inefficient with too many tools, too much data and simply too much to do. According to a study done by IBM, SOC team members are only able to handle half of the alerts that they should be reviewing in a typical workday. This potentially leads to missing the important alerts that are critical to an organization's security. Thus, choosing the right SIEM solution can be transformative for security teams, helping them manage alerts…

IBM and MuleSoft expand global relationship to accelerate modernization on IBM Power 

2 min read - As companies undergo digital transformation, they rely on APIs as the backbone for providing new services and customer experiences. While APIs can simplify application development and deliver integrated solutions, IT shops must have a robust solution to effectively manage and govern them to ensure that response times and costs are kept low for all applications. Many customers use Salesforce’s MuleSoft, named a leader by Gartner® in full lifecycle API management for seven consecutive times, to manage and secure APIs across…

IBM Newsletters

Get our newsletters and topic updates that deliver the latest thought leadership and insights on emerging trends.
Subscribe now More newsletters