You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ismael Juma (JIRA)" <ji...@apache.org> on 2017/10/28 15:59:00 UTC

[jira] [Resolved] (KAFKA-3860) No broker partitions consumed by consumer thread

     [ https://issues.apache.org/jira/browse/KAFKA-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ismael Juma resolved KAFKA-3860.
--------------------------------
    Resolution: Auto Closed

The old consumer is no longer supported, please upgrade to the Java consumer whenever possible.

> No broker partitions consumed by consumer thread
> ------------------------------------------------
>
>                 Key: KAFKA-3860
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3860
>             Project: Kafka
>          Issue Type: Bug
>          Components: consumer
>    Affects Versions: 0.8.2.1
>         Environment: centOS 
>            Reporter: Kundan
>            Assignee: Neha Narkhede
>
> I'm using kakfa-clients-0.8.2.1 to consume messages as Java KafkaConsumer.
> Problem: I have two consumer one consumer is able receive message message but another consumer is unable to receive message and one of the WARNING was visible in log saying that "No broker partitions consumed by consumer thread" and also it was observed that offset was (-1)[selected partitions : mytopic:0: fetched offset = -1: consumed offset = -1] while fetching offset at consumer end.
> Another log was "entering consume " which is kept ZookeeperConsumerConnector.scala file at line 220.
> Other information
> 1) Environment: CentOS
> 2) No of zookeper: 5,
> 3) Properties used to connect zookeeper: 
>      a)zookeeper.connect : zk1:2181,zk2:2181,zk2:2181,zk4:2181,zk5:2181,
>      b)group.id: mygroupId
>      c) fetch.message.max.bytes: 5242880 (Producer side also set)
>      d) auto.commit.enable: false
> 4) Single thread Highlevel consumer code used to consume data.
> 5) Consumer is running in separate VM  Kafka/zookeeper in separate VM
>  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)