[jira] [Commented] (CAMEL-18350) camel-kafka: enabling "breakOnFirstError" causes camel to reconsume all records on error

["Espen Andreassen (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-18350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17610523#comment-17610523 ] 

Espen Andreassen commented on CAMEL-18350:
------------------------------------------

I've confirmed my suspicion. breakOnFirstError = true may cause this on its own. However, it also seems to be dependent on which offset in the series of polled records the error occurs. I've updated the issue title, description, and test to clarify.

> 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
>            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)