conduktor.io ↗

KIP-1336 — Progress Signaling for Share-Group In-Flight Records (markInProgress + IN_PROGRESS State)

Discussion ConsumerProtocolBroker

Introduces a RecordState.IN_PROGRESS state for share-group in-flight records, driven by a new ShareConsumer#markInProgress API and a dedicated MarkInProgressRequest RPC (apiKey 81), plus group.share.in.progress.staleness.threshold.ms and group.share.in.progress.max.lock.extension.ms bounds and an admin.describeShareGroupInFlight query surface. Share groups currently give the broker no signal distinguishing a worker doing genuine long-running work from one that is stuck holding a lock, which blocks adoption for seconds-to-minutes-per-record workloads such as ML inference, external API enrichment, and batch-flushing sinks.

Protocol Impact

ShareAcknowledge

Details

AuthorShekhar Rajak
StatusDiscussion
JIRAKAFKA-20458
WikiView on Apache Wiki
Created2026-05-10
Last Modified2026-05-10
Explore how this KIP affects the Kafka protocol in the Protocol Explorer, or see the full KIP database.