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
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
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
> in
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" wrote:
Can you extend the auto.commit.interval.ms to 5000 ? and retry? Also, why
is your port set to 0?
Regards,
On
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
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/0
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 Coo
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 confi
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
om: 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.
>
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 “defaul
What is your poll time for consumers poll() method?
On Thu, 30 Aug 2018, 16:23 Cristian Petroaca,
wrote:
> 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 topi
Poll timeout is 1000 ms.
On 30/08/2018, 18:28, "M. Manna" wrote:
What is your poll time for consumers poll() method?
On Thu, 30 Aug 2018, 16:23 Cristian Petroaca,
wrote:
> Ok, so I mixed things up a little.
> I started with the kafka Server being configur
Some more weird things:
1. I readded the auto.create.topics.enable=true but now I added the
default.replication.factor=1 and now I did not get the error anymore and
consumer is polling. But then when I removed “default.replication.factor” the
consumer still worked without seeing the group coordi
I added the config “auto.offset.reset” = “earliest” to the consumer and it
receives the messages. So I need to cleanup any persistent data after I do
KafkaServer.shutdown()? How do I do that?
On 31/08/2018, 11:30, "Cristian Petroaca" wrote:
Some more weird things:
1. I readded the auto
13 matches
Mail list logo
