Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Kafka >> mail # user >> Failed to produce message from the second producer


Copy link to this message
-
Re: Failed to produce message from the second producer
It doesn't look like second broker is available. What is the broker list property for each of the producers?

Best,
Priya Matpadi

> On Nov 11, 2013, at 12:12 AM, ji yan <[EMAIL PROTECTED]> 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

 
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB