Log Compaction | Highlights in the Apache Kafka and Stream Processing Community | November 2016 | Confluent
Nov 3, 2016Gwen Shapira

Summary
This post details the rationale for KIP-72 (limiting memory for incoming requests) and KIP-81 (bounding fetch memory usage in consumers), both addressing broker and consumer memory exhaustion. It also discusses KIP-84 (SASL/SCRAM mechanisms) for improved authentication and KIP-85 (dynamic JAAS configuration) for client security in containerized environments. Additionally, KIP-87 (Compaction Tombstone Flag) is introduced as a more robust way to delete keys in compacted topics compared to null values.
More from the Kafka KRaft Migration trail
- Announcing Confluent Platform 8.3: Powerful Apache Flink® SQL operations, Easier KRaft Migrations, Expanded Monitoring and more
- Apache Kafka 4.3 released: 25 KIPs, Kafka Streams, Share Group Controls, Broker Isolation, and more
- Introducing Confluent Platform 8.2: Queues for Kafka & Flink SQL
- Migrate From Hosted Kafka to Confluent Cloud in the KRaft Era
- Apache Kafka 4.1 Release: New Features & Upgrade Guide