You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/04/16 01:16:41 UTC

[jira] [Commented] (KAFKA-5075) Defer exception to the next pollOnce() if consumer's fetch position has already increased

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

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

GitHub user lindong28 opened a pull request:

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

    KAFKA-5075; Defer exception to the next pollOnce() if consumer's fetch position has already increased

    

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

    $ git pull https://github.com/lindong28/kafka KAFKA-5075

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

    https://github.com/apache/kafka/pull/2859.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 #2859
    
----
commit a0d358396c94c6252790920fc80d42d60caf6289
Author: Dong Lin <li...@gmail.com>
Date:   2017-04-15T22:42:26Z

    KAFKA-5075; Defer exception to the next pollOnce() if consumer's fetch position has already increased

----


> Defer exception to the next pollOnce() if consumer's fetch position has already increased
> -----------------------------------------------------------------------------------------
>
>                 Key: KAFKA-5075
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5075
>             Project: Kafka
>          Issue Type: Bug
>          Components: clients, consumer
>    Affects Versions: 0.10.2.0
>            Reporter: Jiangjie Qin
>            Assignee: Dong Lin
>             Fix For: 0.11.0.0
>
>
> In Fetcher.fetchRecords() we iterate over the partition data to collect the ConsumerRecords, after we collect some consumer records from a partition, we advance the position of that partition then move on to the next partition. If the next partition throws exceptions (e.g. OffsetOutOfRangeException), the messages that have already been read out of the buffer will not be delivered to the users. Since the positions of the previous partitions have been be updated, those messages will not be consumed again either.



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