Release Notes - Kafka - Version 0.11.0.2

Below is a summary of the JIRA issues addressed in the 0.11.0.2 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 http://kafka.apache.org/documentation.html.

Bug

• [KAFKA-5140] - Flaky ResetIntegrationTest
• [KAFKA-5967] - Ineffective check of negative value in CompositeReadOnlyKeyValueStore#approximateNumEntries()
• [KAFKA-5970] - Deadlock due to locking of DelayedProduce and group
• [KAFKA-5986] - Streams State Restoration never completes when logging is disabled
• [KAFKA-6003] - Replication Fetcher thread for a partition with no data fails to start
• [KAFKA-6026] - KafkaFuture timeout fails to fire if a narrow race condition is hit
• [KAFKA-6030] - Integer overflow in log cleaner cleanable ratio computation
• [KAFKA-6042] - Kafka Request Handler deadlocks and brings down the cluster.
• [KAFKA-6087] - Scanning plugin.path needs to support relative symlinks
• [KAFKA-6116] - Major performance issue due to excessive logging during leader election
• [KAFKA-6119] - Silent Data Loss in Kafka011 Transactional Producer
• [KAFKA-6131] - Transaction markers are sometimes discarded if txns complete concurrently
• [KAFKA-6134] - High memory usage on controller during partition reassignment
• [KAFKA-6179] - RecordQueue.clear() does not clear MinTimestampTracker's maintained list
• [KAFKA-6190] - GlobalKTable never finishes restoring when consuming transactional messages

Test

• [KAFKA-5725] - Additional failure testing for streams with bouncing brokers