You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Espen Andreassen (Jira)" <ji...@apache.org> on 2022/09/28 13:17:00 UTC
[jira] [Comment Edited] (CAMEL-18350) camel-kafka: enabling "breakOnFirstError" causes camel to reconsume all records on error
[ https://issues.apache.org/jira/browse/CAMEL-18350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17610574#comment-17610574 ]
Espen Andreassen edited comment on CAMEL-18350 at 9/28/22 1:16 PM:
-------------------------------------------------------------------
Seems like you're onto somthing. To clarify, this happens regardless of autoCommit true or false. In my test case autoCommit is true/default (I updated this earlier today).
was (Author: eandre):
Seems like you're onto somthing. To clarify, this happens regardless of autoCommit true or false. In my test case autoCommit is auto (I updated this earlier today).
> camel-kafka: enabling "breakOnFirstError" 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
> Assignee: Karen Lease
> Priority: Minor
> Fix For: 3.20.0
>
>
> {*}Reproducing{*}:
> * Configure camel kafka consumer with with "breakOnFirstError" = "true"
> * Produce a series of records to kafka record consumed by application
> * Ensure offset is commited
> * Produce more records
> * Trigger an error when processing one of the records
> *Expected behavior:*
> * Application should only reconsume records after the last committed offset
> *Actual behavior:*
> * Application reconsumes all records on topic
> Whether the erroneous behavior is triggered seem to be dependent on the offset the failing exchange has internally in the series of records in the poll.
>
> I've created a project on github with a failing test that reproduces the issue: [https://github.com/espeandr/camel-kafka-incorrectly-reconsumes-entire-topic-demo]. I haven't been able to find a pattern to which "message offset" in the poll causes the error. In the test I've reproduced the error by forcing a max poll size as this simplifies the test setup. The issue is also reproducible without overriding maxPollSize.
> I suspect that offset = 0 is committed when breaking out in the erroneous cases.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)