We have recently upgraded some of our applications to use the Kafka 0.8.2
Java producers from the old Java wrappers over Scala producers.
We've noticed these log messages on our application since the upgrade:
2016-01-11T20:56:43.023Z WARN [roducer-network-thread | producer-2]
[s.o.a.kafka.common.network.Selector ] {}: Error in I/O with
my_kafka_host/some_ip
java.io.EOFException: null
at
org.apache.kafka.common.network.NetworkReceive.readFrom(NetworkReceive.java:62)
~[kafka_2.10-0.8.2.2.jar:na]
at org.apache.kafka.common.network.Selector.poll(Selector.java:248)
~[kafka_2.10-0.8.2.2.jar:na]
at
org.apache.kafka.clients.NetworkClient.poll(NetworkClient.java:192)
[kafka_2.10-0.8.2.2jar:na]
at
org.apache.kafka.clients.producer.internals.Sender.run(Sender.java:191)
[kafka_2.10-0.8.2.2.jar:na]
at
org.apache.kafka.clients.producer.internals.Sender.run(Sender.java:122)
[kafka_2.10-0.8.2.2.jar:na]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_66]
They don't occur too often and may be harmless but it is pretty alarming to
see these. It happens with all the brokers we connect to so it doesn't seem
like a problem with a single broker. Our producer config looks a bit like
this:
final Properties config = new Properties();
config.put(ProducerConfig.BOOTSTRAP_SERVERS_CONFIG,
OUR_KAFKA_CONNECT_STRING);
config.put(ProducerConfig.BLOCK_ON_BUFFER_FULL_CONFIG, false); // non
blocking
config.put(ProducerConfig.BUFFER_MEMORY_CONFIG, 10 * 1024 * 1024); // 10
MB
config.put(ProducerConfig.BATCH_SIZE_CONFIG, 16384); // 16 KB
config.put(ProducerConfig.LINGER_MS_CONFIG, 50); // 50 ms
Thanks,
Rajiv
