conduktor.io ↗

KIP-16 — Automated Replica Lag Tuning

Accepted BrokerProducer

Replaces replica.lag.max.messages with time-only ISR eligibility via replica.lag.time.max.ms: a replica is dropped from ISR if it has not caught up to the leader's log end offset within the configured time window. Measuring ISR lag in message count caused high-volume topics to experience spurious ISR shrinks on every large batch (e.g., a single batch exceeding the threshold), while low-volume topics detected dead replicas very slowly.

Details

AuthorAditya Auradkar
StatusAccepted
JIRAKAFKA-1546
WikiView on Apache Wiki
Created2015-03-12
Last Modified2015-07-18
Explore how this KIP affects the Kafka protocol in the Protocol Explorer, or see the full KIP database.