Does the topic exist in both your programmatic broker and remote broker?
Also, are the topic settings same for partitions and replication factor? GROUP_COORDINATOR_NOT_AVAILABLE is enforced as of 0.11.x if the auto-created topic partition/replication-factor setup doesn't match with server's config. So you might want to check all these. Regards, On Wed, 29 Aug 2018 at 15:55, Cristian Petroaca <cpetro...@fitbit.com.invalid> wrote: > Tried it, same problem with 9092. > By the way, the same consumer works with a remote 1.0.1 Kafka broker with > the same config. > There doesn’t seem to be any networking issues with the embedded one since > the consumer successfully sends Find Coordinator messages to it and the > broker responds with Coordinator not found. > > > On 29/08/2018, 17:46, "M. Manna" <manme...@gmail.com> wrote: > > So have you tried binding it to 9092 rather than randomising it, and > see if > that makes any difference? > > On Wed, 29 Aug 2018 at 15:41, Cristian Petroaca > <cpetro...@fitbit.com.invalid> wrote: > > > Port = 0 means Kafka will start listening on a random port which I > need. > > I tried it with 5000 but I get the same result. > > > > > > On 29/08/2018, 16:46, "M. Manna" <manme...@gmail.com> wrote: > > > > Can you extend the auto.commit.interval.ms to 5000 ? and retry? > Also, > > why > > is your port set to 0? > > > > Regards, > > > > On Wed, 29 Aug 2018 at 14:25, Cristian Petroaca > > <cpetro...@fitbit.com.invalid> wrote: > > > > > 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 > > > > > > > > > > > >
