Hi Ryanne, Here is the output of the command:
bin/kafka-consumer-groups --bootstrap-server server --describe --group group_name Error: Executing consumer group command failed due to The consumer group command timed out while waiting for group to initialize The group_name consumer group is not running in the cluster. What is noteworthy is that the consumer group group_name cannot be reset by the CLI (to either latest or earliest) and is still not working way past the retention period of all the topics (from the consumers with latest or earliest auto.offset.reset). Here is the output: bin/kafka-consumer-groups --bootstrap-server server --group group_name --reset-offsets --to-latest --execute Error: Executing consumer group command failed due to The consumer group command timed out while waiting for group to initialize Karim On Tue, Dec 18, 2018 at 8:27 PM Ryanne Dolan <ryannedo...@gmail.com> wrote: > Karim, can you inspect the offsets using kafka-consumer-groups.sh and let > us know what you see? > > Also, is it possible that "group_name" is being used by a consumer group > that is still running? For example, say you have a topic with one partition > and a consumer with "group_name" already. In that case, a second console > consumer with "group_name" wouldn't find any partitions to consume. > > Ryanne > > On Tue, Dec 18, 2018 at 11:18 AM Karim Lamouri <ka...@lamouri.me> wrote: > > > Hi, > > > > One of our brokers went down and when it came back up the consumer of one > > topic couldn’t read using the original consumer group. > > > > This doesn’t output anything: > > > > bin/kafka-console-consumer --bootstrap-server server --topic ASSETS > > --group group_name > > > > However, if I change the name of the group it does output data: > > > > bin/kafka-console-consumer --bootstrap-server server --topic ASSETS > > --group group_name_renamed > > > > Can someone help debug the issue? We are running Kafka 1.1.1 > > > > Thank you > > >
