@Priya, I have two brokers, each running on each of two machines. The
producer broker-list is pointing to the broker server on the same machine
as the producer.
@Jun, I created the topic using kafka-create-topic.sh, the error is
consistently reproduceble
On Mon, Nov 11, 2013 at 9:51 AM, Jun Rao <jun...@gmail.com> wrote:
> Are those ERROR transient? If so, this is normal when the topic didn't
> exist and was auto created.
>
> Thanks,
>
> Jun
>
>
> On Mon, Nov 11, 2013 at 12:12 AM, ji yan <yanj...@gmail.com> wrote:
>
> > Hi Kafka Users
> >
> > I have a test setup at home with one machine hosting a zookeeper server
> and
> > a broker server, while the second machine hosting a broker server.
> >
> > On the first machine, producing and consuming messages are ok. But on the
> > second one, producing message throws this error in the log.
> >
> > The topic test has two partitions and two replicas.
> >
> > [2013-11-11 00:07:24,974] WARN Error while fetching metadata
> > [{TopicMetadata for topic test ->
> > No partition metadata for topic test due to
> > kafka.common.LeaderNotAvailableException}] for topic [test]: class
> > kafka.common.LeaderNotAvailableException
> > (kafka.producer.BrokerPartitionInfo)
> > [2013-11-11 00:07:24,975] ERROR Failed to collate messages by topic,
> > partition due to: Failed to fetch topic metadata for topic: test
> > (kafka.producer.async.DefaultEventHandler)
> >
> > However, when displaying list of topics, I do see a leader for the topic
> >
> > topic: test partition: 0 leader: 0 replicas: 0,1 isr: 0
> > topic: test partition: 1 leader: 0 replicas: 1,0 isr: 0
> >
> > Thanks
> >
>
--
Do not wait to strike till the iron is hot; but make it hot by striking
LinkedIn Profile: http://www.linkedin.com/pub/ji-yan/a/a57/79
