camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CAMEL-10944) camel-kafka - When consumer stop it should auto commit
Date Sun, 05 Mar 2017 17:51:32 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-10944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen resolved CAMEL-10944.
---------------------------------
    Resolution: Fixed

> camel-kafka - When consumer stop it should auto commit
> ------------------------------------------------------
>
>                 Key: CAMEL-10944
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10944
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-kafka
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.19.0
>
>
> When you do a graceful stop of a Kafka route you should be able to auto commit so the
offset is up to date on the broker, so any new consumer that failover, or if you start the
route again, it will pickup from the right spot. Otherwise you have duplicates.
> The kafka consumer will auto commit in the background every 5th sec but if we dont explicit
auto commit on stop then we only have the last offset from the last background thread run
and therefore have much higher chances of duplicates.
> We should add option so users can control if auto commit on stop is sync,async,none
> We should do sync so its forced in case its the JVM shutting down and we cant do async
in the background. And ppl can set it to none if they want as it is today



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message