[jira] [Commented] (KAFKA-2942) Inadvertent auto-commit when pre-fetching can cause message loss

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on KAFKA-2942:
---------------------------------------

GitHub user hachikuji opened a pull request:

    https://github.com/apache/kafka/pull/623

    KAFKA-2942: inadvertent auto-commit when pre-fetching can cause message loss

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/hachikuji/kafka KAFKA-2942

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/623.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #623
    
----
commit 01872110576a82f851e791422f5fec3f797711e7
Author: Jason Gustafson <ja...@confluent.io>
Date:   2015-12-03T06:18:01Z

    KAFKA-2942: inadvertent auto-commit when pre-fetching can cause message loss

----


> Inadvertent auto-commit when pre-fetching can cause message loss
> ----------------------------------------------------------------
>
>                 Key: KAFKA-2942
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2942
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Jason Gustafson
>            Assignee: Jason Gustafson
>
> Before returning from KafkaConsumer.poll(), we update the consumed position and invoke poll(0) to send new fetches. In doing so, it is possible that an auto-commit is triggered which would commit the updated offsets which hasn't yet been returned. If the process then crashes before consuming the messages, there would be a gap in the delivery.



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