Release Notes - Kafka - Version 4.3.1

Below is a summary of the JIRA issues addressed in the 4.3.1 release of Kafka. For full documentation of the release, a guide to get started, and information about the project, see the Kafka project site.

Note about upgrades: Please carefully review the upgrade documentation for this release thoroughly before upgrading your cluster. The upgrade notes discuss any critical information about incompatibilities and breaking changes, performance changes, and any other changes that might impact your production deployment of Kafka.

The documentation for the most recent release can be found at https://kafka.apache.org/documentation.html.

Improvement

  • [KAFKA-20543] - Drop RocksDB offsets column family on clean shutdown when downgrading from 4.3

    • Bug

  • [KAFKA-20605] - upgrade gradle action to enable the CI
  • [KAFKA-20616] - Close-path leaks in RocksDBStore cause native memory growth that eventually leads to OOM
  • [KAFKA-20634] - Spurious HighWatermarkUpdate failed errors in the group coordinator after partition leadership change
  • [KAFKA-20635] - Spurious "Writing records..." failed errors in the group coordinator after partition leadership change
  • [KAFKA-20640] - Consumer group accepts new classic members when migration policy is disabled
  • [KAFKA-20663] - KIP-1035: stale persisted changelog offset causes OffsetOutOfRangeException/TaskCorruptedException on restart
  • [KAFKA-20673] - AdminClient partition-leader APIs hang when a cached leader has left the cluster
  • [KAFKA-20688] - Memory leak in RocksDBTimestampedStoreWithHeaders.openRocksDB when probing column families

    • Task

  • [KAFKA-20535] - Investigate potential improvements to async consumer CPU usage under low max.poll.records
  • [KAFKA-20660] - Add guardrail to detect use of legacy ConsumerRecords constructor via nextOffsets()