You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2022/09/21 11:31:00 UTC
[jira] [Updated] (CAMEL-18350) camel-kafka: combination of breakOnFirstError and maxPollRecords causes camel to reconsume all records on error
[ https://issues.apache.org/jira/browse/CAMEL-18350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-18350:
--------------------------------
Fix Version/s: 3.20.0
(was: 3.19.0)
> camel-kafka: combination of breakOnFirstError and maxPollRecords causes camel to reconsume all records on error
> ----------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-18350
> URL: https://issues.apache.org/jira/browse/CAMEL-18350
> Project: Camel
> Issue Type: Bug
> Components: camel-kafka
> Affects Versions: 3.18.0
> Reporter: Espen Andreassen
> Priority: Minor
> Fix For: 3.20.0
>
>
> *Summary:*
> When configuring the camel consumer with props "breakOnFirstError" = "true" and "maxPollRecords" = "1", camel reconsumes all messages on topic on error. Camel should only have reconsumed the failed message is such cases.
> I configure the component like this to approximate an "exactly once" delivery policy (in comibnation with manual commits).
> I've created a project on github with a failing test that recreates the issue: [https://github.com/espeandr/camel-kafka-incorrectly-reconsumes-entire-topic-demo]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)