You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2015/08/07 16:51:46 UTC

[jira] [Commented] (CAMEL-8653) camel-kafka need to commit the last batch offset when shutdown the consumer

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

Claus Ibsen commented on CAMEL-8653:
------------------------------------

In auto commit mode it now commit the offset when stopping.

In period commit mode, the task is shutdown in doStop but the task is allowed to complete where they will commit the offset.

> camel-kafka need to commit the last batch offset when shutdown the consumer
> ---------------------------------------------------------------------------
>
>                 Key: CAMEL-8653
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8653
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-kafka
>    Affects Versions: 2.15.0, 2.15.1, 2.15.2
>            Reporter: Willem Jiang
>            Priority: Minor
>             Fix For: 2.16.0, 2.15.3
>
>
> Fix of CAMEL-8636 would solve the scenario of when Kafka Broker is shutdown. 
> Client shutdown scenario still results in un-committed offsets from the last batch. 
> For this situation, Offset needs to be commited just before the *Customer* shutdown. Meanwhile some lock mechanism needs to be built with Shutdown hook that would do the following: 
> * Block messages from getting consumed from kafka 
> * Wait for all the messages that are getting processed to be completed. 
> * Commit the Offset 
> * Shutdown the Cosumer



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)