You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Damiano Fontana (Jira)" <ji...@apache.org> on 2021/03/10 08:51:00 UTC
[jira] [Updated] (CAMEL-16327) Kafka Consumer Component always
commits latest offset on shutdown even if autoCommitOnStop == none
[ https://issues.apache.org/jira/browse/CAMEL-16327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Damiano Fontana updated CAMEL-16327:
------------------------------------
Summary: Kafka Consumer Component always commits latest offset on shutdown even if autoCommitOnStop == none (was: Kafka Consumer Component always commits latest offset even if autoCommitOnStop == none)
> Kafka Consumer Component always commits latest offset on shutdown even if autoCommitOnStop == none
> --------------------------------------------------------------------------------------------------
>
> Key: CAMEL-16327
> URL: https://issues.apache.org/jira/browse/CAMEL-16327
> Project: Camel
> Issue Type: Bug
> Affects Versions: 3.6.0, 3.7.0, 3.7.1, 3.7.2, 3.8.0
> Reporter: Damiano Fontana
> Priority: Major
> Fix For: 3.8.0
>
>
> Kafka Consumer Component configured with
> * autoCommitEnable == false
> * allowManualCommit == true
> * autoCommitOnStop == none
> always commits the last seen offset for every partition when route is shut down.
> What's happens is the following:
> # consumer.unsubscribe() is called
> # onPartitionsRevoked() is called
> # commitOffset() with forceCommit == true is called
--
This message was sent by Atlassian Jira
(v8.3.4#803005)