Andras,
Thanks for your feedback!
In my opinion programmatic message sending must work out of the box on the
first try, without any exceptions, warnings or the need for additional
configuration.
I'd be glad to support/contribute.
I agree that the behavior of the producer for the first message o
AFAIK not topics, but only partitions of topics have leaders. What controllers
do you mean? I haven't read about such.
Thanks for the explanation regarding the metadata request, in the meantime I
found out that this is an expected (!) failure
(http://qnalist.com/questions/4787268/kafka-common-l
> > kafka2_1 | [2014-09-26 12:35:07,289] INFO [Kafka Server 2],
> > started (kafka.server.KafkaServer)
> > kafka2_1 | [2014-09-26 12:35:07,394] INFO New leader is 2
> > (kafka.server.ZookeeperLeaderElector$LeaderChangeListener)
The above logs are for controller election. Not le
And the solution was:
Increase retry.backoff.ms from the default 100 ms to 1000 ms, so the output is:
11891 [main] INFO kafka.client.ClientUtils$ - Fetching metadata from broker
id:0,host:192.168.59.103,port:9092 with correlation id 0 for 1 topic(s)
Set(inputTopic)
11893 [main] INFO kafka.prod
Hi,
What does the exception mean in the following context?
I've got two Kafka brokers out which the second one will be elected as leader:
kafka2_1 | [2014-09-26 12:35:07,289] INFO [Kafka Server 2], started
(kafka.server.KafkaServer)
kafka2_1 | [2014-09-26 12:35:07,394] INFO Ne
