kafka-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitry Goldenberg <dgoldenberg...@gmail.com>
Subject Failing to write to Kafka (partitions "don't have a leader")
Date Mon, 28 Sep 2015 23:25:43 GMT
We're running into this issue in a clustered environment where we're trying
to send messages to Kafka and are getting the below error.

Can someone explain what might be causing it and what the error message
means (Failed to send data since partitions [<topic-name>,8] don't have a
leader) ?


WARN kafka.producer.BrokerPartitionInfo: Error while fetching metadata
10 leader: none replicas: isr: isUnderReplicated: false for topic partition
[<topic-name>,10]: [class kafka.common.LeaderNotAvailableException]

ERROR kafka.producer.async.DefaultEventHandler: Failed to send requests for
topics <topic-name> with correlation ids in [2398792,2398801]

ERROR com.acme.core.messaging.kafka.KafkaMessageProducer: Error while
sending a message to the message store.
Failed to send messages after 3 tries.
at kafka.producer.Producer.send(Producer.scala:77)
at kafka.javaapi.producer.Producer.send(Producer.scala:33)

WARN kafka.producer.async.DefaultEventHandler: Failed to send data since
partitions [<topic-name>,8] don't have a leader

What do these errors and warnings mean and how do we get around them?


The code for sending messages is basically as follows:

public class KafkaMessageProducer {
private Producer<String, String> producer;


public void sendMessage(String topic, String key, String message) throws
IOException, MessagingException {
    KeyedMessage<String, String> data = new KeyedMessage<String, String>(
topic, key, message);
    try {
    } catch (Exception ex) {
      throw new MessagingException("Error while sending a message to the
message store.", ex);

Is it possible that the producer gets "stale" and needs to be
re-initialized?  Do we want to re-create the producer on every message (??)
or is it OK to hold on to one indefinitely?


The following are the producer properties that are being set into the

batch.num.messages => 200
client.id => Acme
compression.codec => none
key.serializer.class => kafka.serializer.StringEncoder
message.send.max.retries => 3
metadata.broker.list => data2.acme.com:9092,data3.acme.com:9092
partitioner.class => kafka.producer.DefaultPartitioner
producer.type => sync
queue.buffering.max.messages => 10000
queue.buffering.max.ms => 5000
queue.enqueue.timeout.ms => -1
request.required.acks => 1
request.timeout.ms => 10000
retry.backoff.ms => 1000
send.buffer.bytes => 102400
serializer.class => kafka.serializer.StringEncoder
topic.metadata.refresh.interval.ms => 600000


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message