Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Sun, 5 Mar 2017 17:51:32 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.13048373.1488736042000.2158.1488736292831@Atlassian.JIRA>
In-Reply-To: <JIRA.13048373.1488736042000@Atlassian.JIRA>
References: <JIRA.13048373.1488736042000@Atlassian.JIRA> <JIRA.13048373.1488736042862@jira-lw-us.apache.org>
Subject: [jira] [Resolved] (CAMEL-10944) camel-kafka - When consumer stop it
 should auto commit
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sun, 05 Mar 2017 17:51:36 -0000


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