Thank you, Buntu. On Sat, May 2, 2015 at 1:16 PM, Buntu Dev <buntu...@gmail.com> wrote:
> This seems to be an issue thats fixed in 0.8.2 and after upgrading the > kafka cluster to 0.8.2 this issue was resolved. > https://issues.apache.org/jira/browse/KAFKA-1738 > > <https://issues.apache.org/jira/browse/KAFKA-1738> > > On Fri, May 1, 2015 at 2:58 PM, Dillian Murphey <crackshotm...@gmail.com> > wrote: > > > Hey, not a help, but I just posted the same question. I'm noticing the > > same thing. Where is your hardware? Just curious. I'm running my > > kafka/zookeeper on AWS. > > > > On Tue, Apr 28, 2015 at 10:23 AM, Buntu Dev <buntu...@gmail.com> wrote: > > > > > Also note that the metadata for the topic is missing. I tried creating > > few > > > more topics and all have the same issue. > > > > > > Using the Kafka console producer on the topic, I see these error > messages > > > indicating the missing metadata: > > > > > > WARN Error while fetching metadata [{TopicMetadata for topic my-topic > -> > > > No partition metadata for topic my-topic due to > > > kafka.common.UnknownException}] for topic [my-topic]: class > > > kafka.common.UnknownException (kafka.producer.BrokerPartitionInfo) > > > > > >
