Hi, I'm not sure if your broker and consumer work in different server? May be you can try changing the broker's host.name and the consumer's bootstrap.servers to the broker's really ip-address instead of "127.0.0.1"?
>-----Original Message----- >From: Cristian Petroaca [mailto:cpetro...@fitbit.com.INVALID] >Sent: Wednesday, August 29, 2018 9:25 PM >To: users@kafka.apache.org >Subject: Kafka consumer : Group coordinator lookup failed. The coordinator is >not available > >Hi, > >I’m using the Kafka lib with version 2.11_1.0.1. >I use the KafkaServer.scala class to programmatically create a Kafka instance >and connect it to a programmatically created Zookeeper instance. It has the >following properties: >host.name", "127.0.0.1" >"port", "0" >"zookeeper.connect", "127.0.0.1:" + zooKeeperPort "broker.id", "1" >auto.create.topics.enable", "true" >"delete.topic.enable", "true" > >I then create a new Kafka Consumer with the following properties: >bootstrap.servers", “127.0.0.1” + kafkaPort "auto.commit.interval.ms", "10" >“client_id”, “xxxx” >“enable.auto.commit”, “true” >“auto.commit.interval.ms”, “10” > >My problem is that after I subscribe the consumer to a custom topic, the >consumer just blocks in the .poll() method and I see a lot of messages like: >“Group coordinator lookup failed: The coordinator is not available.” > >I read on another forum that a possible problem is that the >_consumer_offsets topic doesn’t exist but that’s not the case for me. > >Can you suggest a possible root cause? > >Thanks, >Cristian
