conduktor.io ↗

KIP-1343 — Allow opt-in leader-only acknowledgement in DeleteRecords

Discussion ProtocolBrokerAdmin

Adds an opt-in LeaderOnly boolean to the DeleteRecords request so the leader responds with its new logStartOffset immediately after truncating locally, instead of waiting in delayedDeleteRecordsPurgatory for every alive replica to truncate past the requested offset. A single slow follower (GC pause, slow disk, transient network) currently stalls the whole request until it times out with REQUEST_TIMED_OUT, and since a small TimeoutMs is a deadline rather than an acknowledgement mode, callers doing bulk retention sweeps on transient data cannot tell "leader truncated, followers slow" from "leader failed to truncate".

Protocol Impact

ApiVersions · DeleteRecords

Details

AuthorTaiJuWu
StatusDiscussion
JIRAKAFKA-20560
WikiView on Apache Wiki
Created2026-05-16
Last Modified2026-05-21
Explore how this KIP affects the Kafka protocol in the Protocol Explorer, or see the full KIP database.