[
https://issues.apache.org/jira/browse/CAMEL-18350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17610443#comment-17610443
]
Espen Andreassen commented on CAMEL-18350:
------------------------------------------
Just had an incident where this error occurred in a running application. We
first tried increasing the "maxPollRecords" and then enabling autocomit, but
the application still went back to the earliest offset each time an error
occurred. I suspect that "breakOnFirstError" = "true" is all that is needed to
trigger this behavior.
I'll see if I'm able to update the test case to reproduce this behavior and
confirm my suspicion.
> 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)
