Discussion:
Kafka consumer : Group coordinator lookup failed. The coordinator is not available
Cristian Petroaca
2018-08-29 13:24:53 UTC
Permalink
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
M. Manna
2018-08-29 13:46:09 UTC
Permalink
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
Post by Cristian Petroaca
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.
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"
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
“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
Cristian Petroaca
2018-08-29 14:40:43 UTC
Permalink
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" <***@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
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.
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"
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
“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
M. Manna
2018-08-29 14:45:58 UTC
Permalink
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
Post by Cristian Petroaca
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.
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
Post by Cristian Petroaca
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.
Post by Cristian Petroaca
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"
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
Post by Cristian Petroaca
consumer just blocks in the .poll() method and I see a lot of
“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
Cristian Petroaca
2018-08-29 14:54:51 UTC
Permalink
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" <***@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
Post by Cristian Petroaca
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.
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
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.
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"
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
“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
M. Manna
2018-08-29 15:05:29 UTC
Permalink
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
Post by Cristian Petroaca
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.
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
Post by Cristian Petroaca
Port = 0 means Kafka will start listening on a random port which I
need.
Post by Cristian Petroaca
I tried it with 5000 but I get the same result.
Can you extend the auto.commit.interval.ms to 5000 ? and retry?
Also,
Post by Cristian Petroaca
why
is your port set to 0?
Regards,
On Wed, 29 Aug 2018 at 14:25, Cristian Petroaca
Post by Cristian Petroaca
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
Post by Cristian Petroaca
Post by Cristian Petroaca
instance and connect it to a programmatically created Zookeeper
instance.
Post by Cristian Petroaca
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
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,
Post by Cristian Petroaca
the
Post by Cristian Petroaca
consumer just blocks in the .poll() method and I see a lot of
“Group coordinator lookup failed: The coordinator is not
available.”
Post by Cristian Petroaca
Post by Cristian Petroaca
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.
Post by Cristian Petroaca
Post by Cristian Petroaca
Can you suggest a possible root cause?
Thanks,
Cristian
Cristian Petroaca
2018-08-30 08:24:44 UTC
Permalink
Yes.
In my programmatic env I first create it with:
AdminUtils.createTopic(zkUtils, topic, 1, 1, new Properties(), RackAwareMode.Enforced$.MODULE$);
So partitions = 1 and replication = 1.

The same for the remote broker, I created the topic –partitions 1 –replication-factor 1

Are there any other reasons for that error?

On 29/08/2018, 18:06, "M. Manna" <***@gmail.com> wrote:

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
Post by Cristian Petroaca
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.
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
Post by Cristian Petroaca
Port = 0 means Kafka will start listening on a random port which I
need.
Post by Cristian Petroaca
I tried it with 5000 but I get the same result.
Can you extend the auto.commit.interval.ms to 5000 ? and retry?
Also,
Post by Cristian Petroaca
why
is your port set to 0?
Regards,
On Wed, 29 Aug 2018 at 14:25, Cristian Petroaca
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
Post by Cristian Petroaca
instance and connect it to a programmatically created Zookeeper
instance.
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
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,
Post by Cristian Petroaca
the
consumer just blocks in the .poll() method and I see a lot of
“Group coordinator lookup failed: The coordinator is not
available.”
Post by Cristian Petroaca
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.
Post by Cristian Petroaca
Can you suggest a possible root cause?
Thanks,
Cristian
Cristian Petroaca
2018-08-30 15:23:29 UTC
Permalink
Ok, so I mixed things up a little.
I started with the kafka Server being configured to auto create topics. That gave the error.
But turning the auto create off and creating the topic with AdminUtils does not show the error and the consumer actually polls for messages.
I did not modify the “default.replication.factor” for auto created topics and that has as default 1. So I’m not sure why I would see the error in the first place?

Even though I don’t see the error anymore and my consumer polls for messages, it does not receive any messages. I am waiting a reasonable amount of time (1min) after the producer created the messages.
An independent console consumer connected to the same borker and topic does receive them.
My consumer config does not seem exotic as in to create such a situation. Any reason for not receiving messages?

Thanks

On 30/08/2018, 11:25, "Cristian Petroaca" <***@fitbit.com.INVALID> wrote:

Yes.
In my programmatic env I first create it with:
AdminUtils.createTopic(zkUtils, topic, 1, 1, new Properties(), RackAwareMode.Enforced$.MODULE$);
So partitions = 1 and replication = 1.

The same for the remote broker, I created the topic –partitions 1 –replication-factor 1

Are there any other reasons for that error?

On 29/08/2018, 18:06, "M. Manna" <***@gmail.com> wrote:

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
Post by Cristian Petroaca
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.
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
Post by Cristian Petroaca
Port = 0 means Kafka will start listening on a random port which I
need.
Post by Cristian Petroaca
I tried it with 5000 but I get the same result.
Can you extend the auto.commit.interval.ms to 5000 ? and retry?
Also,
Post by Cristian Petroaca
why
is your port set to 0?
Regards,
On Wed, 29 Aug 2018 at 14:25, Cristian Petroaca
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
Post by Cristian Petroaca
instance and connect it to a programmatically created Zookeeper
instance.
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
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,
Post by Cristian Petroaca
the
consumer just blocks in the .poll() method and I see a lot of
“Group coordinator lookup failed: The coordinator is not
available.”
Post by Cristian Petroaca
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.
Post by Cristian Petroaca
Can you suggest a possible root cause?
Thanks,
Cristian
M. Manna
2018-08-30 15:27:47 UTC
Permalink
What is your poll time for consumers poll() method?
Post by Cristian Petroaca
Ok, so I mixed things up a little.
I started with the kafka Server being configured to auto create topics.
That gave the error.
But turning the auto create off and creating the topic with AdminUtils
does not show the error and the consumer actually polls for messages.
I did not modify the “default.replication.factor” for auto created topics
and that has as default 1. So I’m not sure why I would see the error in the
first place?
Even though I don’t see the error anymore and my consumer polls for
messages, it does not receive any messages. I am waiting a reasonable
amount of time (1min) after the producer created the messages.
An independent console consumer connected to the same borker and topic does receive them.
My consumer config does not seem exotic as in to create such a situation.
Any reason for not receiving messages?
Thanks
Yes.
AdminUtils.createTopic(zkUtils, topic, 1, 1, new Properties(),
RackAwareMode.Enforced$.MODULE$);
So partitions = 1 and replication = 1.
The same for the remote broker, I created the topic –partitions 1
–replication-factor 1
Are there any other reasons for that error?
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
Post by Cristian Petroaca
Tried it, same problem with 9092.
By the way, the same consumer works with a remote 1.0.1 Kafka
broker with
Post by Cristian Petroaca
the same config.
There doesn’t seem to be any networking issues with the embedded
one since
Post by Cristian Petroaca
the consumer successfully sends Find Coordinator messages to it
and the
Post by Cristian Petroaca
broker responds with Coordinator not found.
So have you tried binding it to 9092 rather than randomising
it, and
Post by Cristian Petroaca
see if
that makes any difference?
On Wed, 29 Aug 2018 at 15:41, Cristian Petroaca
Post by Cristian Petroaca
Port = 0 means Kafka will start listening on a random port
which I
Post by Cristian Petroaca
need.
Post by Cristian Petroaca
I tried it with 5000 but I get the same result.
Can you extend the auto.commit.interval.ms to 5000 ?
and retry?
Post by Cristian Petroaca
Also,
Post by Cristian Petroaca
why
is your port set to 0?
Regards,
On Wed, 29 Aug 2018 at 14:25, Cristian Petroaca
Post by Cristian Petroaca
Hi,
I’m using the Kafka lib with version 2.11_1.0.1.
I use the KafkaServer.scala class to
programmatically create a
Post by Cristian Petroaca
Kafka
Post by Cristian Petroaca
Post by Cristian Petroaca
instance and connect it to a programmatically
created Zookeeper
Post by Cristian Petroaca
Post by Cristian Petroaca
instance.
Post by Cristian Petroaca
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
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
Post by Cristian Petroaca
topic,
Post by Cristian Petroaca
the
Post by Cristian Petroaca
consumer just blocks in the .poll() method and I see
a lot of
Post by Cristian Petroaca
Post by Cristian Petroaca
Post by Cristian Petroaca
“Group coordinator lookup failed: The coordinator is
not
Post by Cristian Petroaca
available.”
Post by Cristian Petroaca
Post by Cristian Petroaca
I read on another forum that a possible problem is
that the
Post by Cristian Petroaca
Post by Cristian Petroaca
Post by Cristian Petroaca
_consumer_offsets topic doesn’t exist but that’s not
the case
Post by Cristian Petroaca
for me.
Post by Cristian Petroaca
Post by Cristian Petroaca
Can you suggest a possible root cause?
Thanks,
Cristian
Cristian Petroaca
2018-08-31 07:11:50 UTC
Permalink
Poll timeout is 1000 ms.

On 30/08/2018, 18:28, "M. Manna" <***@gmail.com> wrote:

What is your poll time for consumers poll() method?
Post by Cristian Petroaca
Ok, so I mixed things up a little.
I started with the kafka Server being configured to auto create topics.
That gave the error.
But turning the auto create off and creating the topic with AdminUtils
does not show the error and the consumer actually polls for messages.
I did not modify the “default.replication.factor” for auto created topics
and that has as default 1. So I’m not sure why I would see the error in the
first place?
Even though I don’t see the error anymore and my consumer polls for
messages, it does not receive any messages. I am waiting a reasonable
amount of time (1min) after the producer created the messages.
An independent console consumer connected to the same borker and topic does receive them.
My consumer config does not seem exotic as in to create such a situation.
Any reason for not receiving messages?
Thanks
Yes.
AdminUtils.createTopic(zkUtils, topic, 1, 1, new Properties(),
RackAwareMode.Enforced$.MODULE$);
So partitions = 1 and replication = 1.
The same for the remote broker, I created the topic –partitions 1
–replication-factor 1
Are there any other reasons for that error?
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
Post by Cristian Petroaca
Tried it, same problem with 9092.
By the way, the same consumer works with a remote 1.0.1 Kafka
broker with
Post by Cristian Petroaca
the same config.
There doesn’t seem to be any networking issues with the embedded
one since
Post by Cristian Petroaca
the consumer successfully sends Find Coordinator messages to it
and the
Post by Cristian Petroaca
broker responds with Coordinator not found.
So have you tried binding it to 9092 rather than randomising
it, and
Post by Cristian Petroaca
see if
that makes any difference?
On Wed, 29 Aug 2018 at 15:41, Cristian Petroaca
Post by Cristian Petroaca
Port = 0 means Kafka will start listening on a random port
which I
Post by Cristian Petroaca
need.
Post by Cristian Petroaca
I tried it with 5000 but I get the same result.
Can you extend the auto.commit.interval.ms to 5000 ?
and retry?
Post by Cristian Petroaca
Also,
Post by Cristian Petroaca
why
is your port set to 0?
Regards,
On Wed, 29 Aug 2018 at 14:25, Cristian Petroaca
Hi,
I’m using the Kafka lib with version 2.11_1.0.1.
I use the KafkaServer.scala class to
programmatically create a
Post by Cristian Petroaca
Kafka
Post by Cristian Petroaca
instance and connect it to a programmatically
created Zookeeper
Post by Cristian Petroaca
Post by Cristian Petroaca
instance.
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
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
Post by Cristian Petroaca
topic,
Post by Cristian Petroaca
the
consumer just blocks in the .poll() method and I see
a lot of
Post by Cristian Petroaca
Post by Cristian Petroaca
“Group coordinator lookup failed: The coordinator is
not
Post by Cristian Petroaca
available.”
Post by Cristian Petroaca
I read on another forum that a possible problem is
that the
Post by Cristian Petroaca
Post by Cristian Petroaca
_consumer_offsets topic doesn’t exist but that’s not
the case
Post by Cristian Petroaca
for me.
Post by Cristian Petroaca
Can you suggest a possible root cause?
Thanks,
Cristian
Cristian Petroaca
2018-08-31 08:30:45 UTC
Permalink
This post might be inappropriate. Click to display it.
Cristian Petroaca
2018-08-31 09:07:08 UTC
Permalink
This post might be inappropriate. Click to display it.
赖剑清
2018-08-30 08:43:24 UTC
Permalink
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-----
Sent: Wednesday, August 29, 2018 9:25 PM
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
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"
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
“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?
T
Loading...