That error indicates the broker closed the connection for some reason. Any
useful logs from the broker? It looks like you're using ELB, which could
also be the culprit. A connection timeout seems doubtful, but ELB can also
close connections for other reasons, like failed health checks.
-Ewen
On
You could be right Ewen. I was starting to wonder about the load balancer
too. Is using a load balancer a bad idea? How else do users know which
kafka broker to connect to?
I'm using one of the IPs directly and I don't see that error. I am seeing
an occasional connection refused. What the heck.
I'm a new user/admin to kafka. I'm running a 3 node ZK and a 6 brokers on
aws.
The performance I'm seeing is shockingly bad. I need some advice!
bin/kafka-run-class.sh org.apache.kafka.clients.tools.ProducerPerformance
test2 5000 100 -1 acks=1 bootstrap.servers=5myloadbalancer:9092
I was running the performance command from a virtual box server, so that
seems like it was part of the problem. I'm getting better results running
this on a server on aws, but that's kind of expected. Can you look at
these results, and comment on the occasional warning I see? I appreciate
it!
Where are you running ProducerPerformance in relation to ZK and the Kafka
brokers? You should definitely see much higher performance than this.
A couple of other things I can think of that might be going wrong: Are all
your VMs in the same AZ? Are you storing Kafka data in EBS or local
ephemeral
