conduktor.io ↗

KIP-354 — Add a Maximum Log Compaction Lag

Accepted Kafka 2.3 Broker

Adds a max.compaction.lag.ms topic configuration that guarantees a dirty log segment will be compacted within a specified time, regardless of the dirty ratio. Without a maximum lag, GDPR-style delete markers (tombstones) could remain in the log indefinitely if the dirty ratio never reached the min.cleanable.dirty.ratio threshold, violating data deletion SLAs.

Details

Authorxiongqi wu
StatusAccepted
Kafka Version2.3
JIRAKAFKA-7321
WikiView on Apache Wiki
Created2018-08-09
Last Modified2018-12-06
Explore how this KIP affects the Kafka protocol in the Protocol Explorer, or see the full KIP database.