KIP-1206 — Strict max fetch records in share fetch
Accepted Kafka 4.2 Consumer
Changes the maxFetchRecords limit in ShareFetch from a soft limit (batch-boundary aligned) to a strict record-count limit, ensuring the number of records returned never exceeds the configured value. The soft limit caused unpredictable batch sizes for share consumers with long per-record processing times, leading to frequent acquisition lock timeouts and uncontrolled redelivery.
Protocol Impact
ShareFetch v2 · Fetch
Details
| Author | Jimmy Wang |
| Status | Accepted |
| Kafka Version | 4.2 |
| JIRA | KAFKA-19020 |
| Wiki | View on Apache Wiki |
| Created | 2025-08-18 |
| Last Modified | 2025-11-26 |
Explore how this KIP affects the Kafka protocol in the Protocol Explorer, or see the full KIP database.