KIP-1317 — Mandatory DLQ Disposition Header for Share Groups
Discussion BrokerConsumer
Requires the share group coordinator to write standardized headers on every DLQ record — `_dlq.errors.disposition` plus original topic, partition, offset, consumer group and ISO-8601 timestamp — with disposition values such as MAX_DELIVERY_ATTEMPTS_REACHED, CLIENT_REJECTED and CIRCUIT_BREAKER_ARCHIVED. KIP-1191 does not persist the routing reason the broker already knows, so a poison pill is indistinguishable from an explicit NACK or a transient infrastructure failure, forcing operators to correlate DLQ offsets against broker logs and blocking automated replay tooling.
Details
| Author | ViquarKhan |
| Status | Discussion |
| Wiki | View on Apache Wiki |
| Created | 2026-03-08 |
| Last Modified | 2026-04-06 |
Explore how this KIP affects the Kafka protocol in the Protocol Explorer, or see the full KIP database.