Hi Raja,
Thanks a lot for that input. It definitely was a problem with the
__consumer_offsets not getting updated (not sure why that didnt happen
though with upgrading kafka with a new release).
But I deleted the __consumer_offsets topic and it was auto created and the
consumer offset checker work
Hi Meghana,
We also faced similar issue and found that it returned
ConsumerCoordinatorNotAvailableCode always for one broker (server id 3) and
leader for all partitions of __consumer_offsets topic is same broker id 3.
So wiped off kafka data dir on that broker and restarted it. After that
Consume
Hi Mayuresh,
A few more inputs that I can provide at the moment after some testing are
as follows.
1. The error returned by the consumer offset checker's
ConsumerMetadataResponse is "ConsumerCoordinatorNotAvailableCode". Could it
somehow be related to the offsets being written to zookeeper and not
Hi Meghana,
Let me try this out on my cluster that has latest trunk deployed.
Thanks,
Mayuresh
On Mon, May 11, 2015 at 1:53 PM, Meghana Narasimhan <
mnarasim...@bandwidth.com> wrote:
> Hi Mayuresh,
> A small update. The Kafka version I'm currently using is 2.10-0.8.2.1 (not
> 2.11 as previous
Hi Mayuresh,
A small update. The Kafka version I'm currently using is 2.10-0.8.2.1 (not
2.11 as previously mentioned). The cluster looks fine. Not sure why the
consumer offset checker does not return a valid output and gets stuck.
bin/kafka-topics.sh --describe --zookeeper localhost:2181 --topic
Hi,
I'm using the Kafka 8.2.1 version(kafka_2.11-0.8.2.1) and the consumer
offset checker hangs indefinitely and does not return any results. I
enabled the debug for tools and below is the debug statements as seen on
the stdout. Any thoughts or inputs on this will be much appreciated.
command used
Hi Mayuresh,
Yes, the broker is up and accepting connections. Multiple consumers are
consuming off topics on the broker.
Also I am seeing the issue only with this particular version (2.11-0.8.2.1).
It worked fine with the beta that I was using earlier.
On Fri, May 8, 2015 at 12:45 PM, Mayuresh G
Is X.X.X.X:9092 up and accepting connections?
I am confused aas in why is it not connecting some other broker if
connection to this broker fails. Can you check if the broker is up?
The way it works is the consumer will send a ConsumerMetadataRequest to one
of the brokers and get the offsetmanager
Hi,
I'm using the Kafka 8.2.1 version(kafka_2.11-0.8.2.1) and the consumer
offset checker hangs indefinitely and does not return any results. I
enabled the debug for tools and below is the debug statements as seen on
the stdout. Any thoughts or inputs on this will be much appreciated.
command used
