Hi Stevo, There are a couple of options to verify the topic exists:
1. Consume from a topic with "offsets.storage=kafka". If its not created already, this should create it. 2. List and describe the topic using the Kafka topics script. Ex: bin/kafka-topics.sh --zookeeper localhost:2181 --list bin/kafka-topics.sh --zookeeper localhost:2181 --describe --topic __consumer_offsets 1. Check the ZNode exists in Zookeeper. Ex: bin/zookeeper-shell.sh localhost:2181 ls /brokers/topics/__consumer_offsets get /brokers/topics/__consumer_offsets Thanks, Grant On Mon, Oct 5, 2015 at 10:44 AM, Stevo Slavić <ssla...@gmail.com> wrote: > Hello Apache Kafka community, > > In my integration tests, with single 0.8.2.2 broker, for newly created > topic with single partition, after determining through topic metadata > request that partition has lead broker assigned, when I try to reset offset > for given consumer group, I first try to discover offset coordinator and > that lookup is throwing ConsumerCoordinatorNotAvailableException > > On > > https://cwiki.apache.org/confluence/display/KAFKA/A+Guide+To+The+Kafka+Protocol#AGuideToTheKafkaProtocol-OffsetCommit/FetchAPI > it is documented that broker returns ConsumerCoordinatorNotAvailableCode > for consumer metadata requests or offset commit requests if the offsets > topic has not yet been created. > > I wonder if this is really the case, that the offsets topic has not been > created. Any tips how to ensure/verify that offsets topic exists? > > Kind regards, > > Stevo Slavic. > -- Grant Henke Software Engineer | Cloudera gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
