You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Lan Ding (Jira)" <ji...@apache.org> on 2025/07/04 06:43:00 UTC

[jira] [Updated] (KAFKA-19469) Share group supports dead letter queue

     [ https://issues.apache.org/jira/browse/KAFKA-19469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lan Ding updated KAFKA-19469:
-----------------------------
    Description: 
In the current Share Group logic, if the consumer cannot process a record and the delivery count reaches the delivery attempt limit, the record moves into an Archived state and is not eligible for additional delivery attempts.

In reality, the Dead Letter queue would be better suited for handling this scenario.

  was:
In the current Share Group logic, if the consumer cannot process a record and the delivery count reaches the delivery attempt limit, the record moves into an Archived state and is not eligible for additional delivery attempts.

In reality, a dead letter queue would be better suited for handling this scenario.


> Share group supports dead letter queue
> --------------------------------------
>
>                 Key: KAFKA-19469
>                 URL: https://issues.apache.org/jira/browse/KAFKA-19469
>             Project: Kafka
>          Issue Type: New Feature
>            Reporter: Lan Ding
>            Priority: Major
>              Labels: need-kip
>
> In the current Share Group logic, if the consumer cannot process a record and the delivery count reaches the delivery attempt limit, the record moves into an Archived state and is not eligible for additional delivery attempts.
> In reality, the Dead Letter queue would be better suited for handling this scenario.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)