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/06/01 10:15:04 UTC

[jira] [Commented] (KAFKA-5327) Console Consumer should only poll for up to max messages

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

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

Github user amethystic closed the pull request at:

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


> Console Consumer should only poll for up to max messages
> --------------------------------------------------------
>
>                 Key: KAFKA-5327
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5327
>             Project: Kafka
>          Issue Type: Improvement
>          Components: tools
>            Reporter: Dustin Cote
>            Assignee: huxi
>            Priority: Minor
>
> The ConsoleConsumer has a --max-messages flag that can be used to limit the number of messages consumed. However, the number of records actually consumed is governed by max.poll.records. This means you see one message on the console, but your offset has moved forward a default of 500, which is kind of counterintuitive. It would be good to only commit offsets for messages we have printed to the console.



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