Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Error Strategy LOG_AND_RESUME_AT_NEXT_RECORD to enable DLQs #1067

Open
jdeex opened this issue Sep 5, 2024 · 0 comments
Open

New Error Strategy LOG_AND_RESUME_AT_NEXT_RECORD to enable DLQs #1067

jdeex opened this issue Sep 5, 2024 · 0 comments

Comments

@jdeex
Copy link
Contributor

jdeex commented Sep 5, 2024

Feature description

Sometimes Retrying is not an option, you want to skip the message and continue and perhaps let another consumer deal with the failed messages. The documentation currently recommends that for the RESUME_AT_NEXT_RECORD error strategy, but each developer has to code that. There are some issues with that too: #110

It would be great to:

  • Divert error messages to a configured DLQ (Dead Letter Queue)
  • Include the error/exception in a header
  • Include the topic/offset/partition where the failed messages was
  • and resume on next record

Configuration:

@KafkaListener(
    value = "myGroup",
    errorStrategy = @ErrorStrategy(
        value = ErrorStrategyValue.LOG_AND_RESUME_AT_NEXT_RECORD,
        dlq = "${my.dlq.topic.name}"
    )
)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant