Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-3860

No broker partitions consumed by consumer thread

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Auto Closed
    • 0.8.2.1
    • None
    • consumer
    • None
    • centOS

    Description

      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

      Attachments

        Activity

          People

            nehanarkhede Neha Narkhede
            kundantre Kundan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: